Triple
T9889610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banliang coin |
E181419
|
entity |
| Predicate | valueRelativeToLiang |
P51035
|
FINISHED |
| Object | 0.5 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 0.5 | Statement: [Banliang coin, valueRelativeToLiang, 0.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueRelativeToLiang Context triple: [Banliang coin, valueRelativeToLiang, 0.5]
-
A.
valueOfL
Indicates that one entity represents the numerical or quantitative value associated with another entity, typically in a specific context or measurement.
-
B.
valueRelativeToMainUnit
chosen
Indicates how a value is expressed in relation to a primary or reference unit, such as a main measurement or base quantity.
-
C.
valueAt
Indicates that one entity specifies the value or content associated with another entity at a particular point, position, or context.
-
D.
relativeLength
Indicates a comparative relationship between entities based on how long they are relative to one another.
-
E.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb47be2988190811a99dc56ae542a |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:39 p.m.