Triple
T32385024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Qin |
E827523
|
entity |
| Predicate | hasFamousHolder |
P1918
|
FINISHED |
| Object | Qin Shi Huang |
—
|
NE NERFINISHED |
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: Qin Shi Huang | Statement: [King of Qin, hasFamousHolder, Qin Shi Huang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamousHolder Context triple: [King of Qin, hasFamousHolder, Qin Shi Huang]
-
A.
mostNotableHolder
Indicates that one entity is the most prominent or distinguished bearer or possessor of another entity (such as a title, record, or role) compared to all other holders.
-
B.
hasFamousPass
Indicates that an entity possesses or is associated with a well-known or historically significant pass (such as a route, corridor, or access point).
-
C.
notableHolder
chosen
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
D.
hasFamousReligiousBearer
Indicates that an entity has at least one well-known religious figure associated with or bearing its name.
-
E.
notableModernHolder
Indicates that an entity is a prominent or distinguished contemporary bearer or possessor of another entity (such as a title, position, or distinction).
- 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_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 1, 2026, 12:51 a.m.