Triple
T27766697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hànshū |
E701618
|
entity |
| Predicate | hasImportantTreatiseOn |
P70202
|
FINISHED |
| Object | salt and iron |
—
|
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: salt and iron | Statement: [Hànshū, hasImportantTreatiseOn, salt and iron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportantTreatiseOn Context triple: [Hànshū, hasImportantTreatiseOn, salt and iron]
-
A.
isSeminalWorkFor
Indicates that one work is a foundational or highly influential source for another work, significantly shaping its development or direction.
-
B.
notableWorkDiscussed
chosen
Indicates that a particular work (such as a book, film, or artwork) is the subject of discussion, analysis, or commentary in relation to another entity.
-
C.
isSeminalWorkOf
Indicates that a work is a foundational or highly influential creation associated with a particular person, field, or body of work.
-
D.
workOfPhilosopher
Indicates that the subject is a philosophical work created or authored by the philosopher represented by the object.
-
E.
notableWorkWrittenThere
Indicates that a notable work was written at or in the specified place.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 4:31 p.m.