Triple
T32792800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Later Three Kingdoms |
E838675
|
entity |
| Predicate | mainPolities |
P139424
|
FINISHED |
| Object | Later Baekje |
—
|
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: Later Baekje | Statement: [Later Three Kingdoms, mainPolities, Later Baekje]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPolities Context triple: [Later Three Kingdoms, mainPolities, Later Baekje]
-
A.
memberPolities
chosen
Indicates that one polity is a constituent or member entity within a larger political grouping, organization, or union.
-
B.
hasPolity
Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
-
C.
linkedPolities
Indicates that two political entities are connected by some defined relationship, such as alliance, dependency, or shared governance.
-
D.
politicalSphere
Indicates involvement or relevance within the domain of politics, governance, or public policy activities and interactions.
-
E.
geopoliticalOrganization
Indicates that an entity functions as a political or governmental body associated with a specific geographic region or territory.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:14 a.m.