Triple
T34726878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geumgwan Gaya |
E1001094
|
entity |
| Predicate | leadingPolityOf |
P126117
|
FINISHED |
| Object | Gaya confederacy |
—
|
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: Gaya confederacy | Statement: [Geumgwan Gaya, leadingPolityOf, Gaya confederacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadingPolityOf Context triple: [Geumgwan Gaya, leadingPolityOf, Gaya confederacy]
-
A.
laterPoliticalSystemUnderRule
Indicates that one political system came under the rule or authority of another political system at a later point in time.
-
B.
politicalEntityPrecursorOf
chosen
Indicates that one political entity historically preceded and contributed to the formation, evolution, or establishment of another political entity.
-
C.
linkedPolities
Indicates that two political entities are connected by some defined relationship, such as alliance, dependency, or shared governance.
-
D.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
E.
formerSovereign
Indicates that an entity once held sovereign (ruling) authority over another entity but no longer does.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.