Triple
T37666113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cap Kingdom |
E937822
|
entity |
| Predicate | startingKingdomFor |
P203190
|
FINISHED |
| Object | Mario |
—
|
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: Mario | Statement: [Cap Kingdom, startingKingdomFor, Mario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingKingdomFor Context triple: [Cap Kingdom, startingKingdomFor, Mario]
-
A.
clientKingdomOf
Indicates a relationship where one kingdom is politically subordinate or tributary to another, more powerful kingdom while retaining limited internal autonomy.
-
B.
foundingRulerInvitingSettlement
Indicates that a founding ruler initiates or invites the establishment of a new settlement or community.
-
C.
foundedKingdom
Indicates that an entity established or created a kingdom as its founder.
-
D.
overkingdomOf
Indicates that one kingdom holds overarching authority or sovereignty over another kingdom.
-
E.
mentionsKingdom
Indicates that one entity explicitly refers to or brings up the topic of a kingdom in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0136e4af808190b529d324bbf0c5d9 |
completed | May 11, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_6a01369141c4819091cb8064913a44ca |
completed | May 11, 2026, 1:53 a.m. |
| PDg | Predicate description generation | batch_6a0136e3d6ec8190898b5ab5a628a99d |
completed | May 11, 2026, 1:54 a.m. |
Created at: May 3, 2026, 4:18 p.m.