Triple
T32385235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ban Liang inscription |
E827528
|
entity |
| Predicate | typeOfValueIndicated |
P176065
|
FINISHED |
| Object | weight-based denomination |
—
|
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: weight-based denomination | Statement: [Ban Liang inscription, typeOfValueIndicated, weight-based denomination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfValueIndicated Context triple: [Ban Liang inscription, typeOfValueIndicated, weight-based denomination]
-
A.
typeOfValue
Indicates that one entity specifies the kind or category of value associated with another entity.
-
B.
valueExpressed
Indicates that a particular value, opinion, or quantitative measure is articulated, represented, or made explicit by an entity or expression.
-
C.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
D.
variableType
Indicates that one entity is the type or data category of the other entity, which is a variable.
-
E.
valueElementType
chosen
Indicates that one entity specifies the type or category of value associated with another entity.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0056174c908190be99c91a70393e47 |
completed | May 10, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_6a00538e7e08819091ecd4316cd641a1 |
completed | May 10, 2026, 9:44 a.m. |
Created at: May 1, 2026, 12:51 a.m.