Triple
T32385445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clerical Script |
E827533
|
entity |
| Predicate | developedInDynasty |
P164412
|
FINISHED |
| Object | Qin dynasty |
—
|
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 dynasty | Statement: [Clerical Script, developedInDynasty, Qin dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedInDynasty Context triple: [Clerical Script, developedInDynasty, Qin dynasty]
-
A.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
-
B.
formedDynasty
Indicates that an entity established or created a ruling dynasty.
-
C.
partOfDynasty
Indicates that an entity belongs to, or is a constituent member of, a particular dynasty.
-
D.
basedOnDynasty
Indicates that something is derived from, influenced by, or established on the foundation of a particular dynasty.
-
E.
existedUnderDynasty
chosen
Indicates that an entity existed or was in effect during the period of a specified dynasty’s rule.
- 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_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 12:51 a.m.