Triple
T27848953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Su |
E703897
|
entity |
| Predicate | hasNotableDynastyAssociationThroughBearers |
P196832
|
FINISHED |
| Object | Song 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: Song dynasty | Statement: [Su, hasNotableDynastyAssociationThroughBearers, Song dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDynastyAssociationThroughBearers Context triple: [Su, hasNotableDynastyAssociationThroughBearers, Song dynasty]
-
A.
hasNotableDynastyMember
Indicates that a dynasty includes at least one member who is historically or culturally notable.
-
B.
hasNameBearersInDynasty
chosen
Indicates that the name in question is borne by individuals belonging to a specified dynasty.
-
C.
hasNotableMaleBearer
Indicates that an entity has at least one well-known or prominent male individual associated with bearing its name or title.
-
D.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
E.
belongsToDynasticHistory
Indicates that something is part of, or associated with, a particular dynastic historical period or lineage.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: April 27, 2026, 6:09 p.m.