Triple
T27957562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fu Hao |
E703591
|
entity |
| Predicate | nameWrittenOn |
P10347
|
FINISHED |
| Object | bronze inscriptions |
—
|
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: bronze inscriptions | Statement: [Fu Hao, nameWrittenOn, bronze inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameWrittenOn Context triple: [Fu Hao, nameWrittenOn, bronze inscriptions]
-
A.
nameWrittenIn
Indicates that an entity’s name is written or recorded using a specified language, script, or writing system.
-
B.
areWrittenOn
chosen
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
-
C.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
D.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
E.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:29 p.m.