Triple
T8798917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon King |
E209351
|
entity |
| Predicate | Four Dragon KingsRule |
P68921
|
FINISHED |
| Object | Four Seas |
—
|
LITERAL FINISHED |
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: Four Seas | Statement: [Dragon King, Four Dragon KingsRule, Four Seas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Four Dragon KingsRule Context triple: [Dragon King, Four Dragon KingsRule, Four Seas]
-
A.
يحكمها
Indicates that an entity governs, rules, or exercises authority over another entity.
-
B.
realmRuled
chosen
Indicates that one entity serves as the sovereign or governing ruler over a particular realm, territory, or domain.
-
C.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
D.
compiledUnderReignOf
Indicates that something (such as a document, code, or work) was compiled or put together during the period when a particular ruler or authority was in power.
-
E.
wasKingdom
Indicates that one entity functioned as the sovereign kingdom or ruling polity of another entity during a particular period.
- 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_69ca836240888190a62b262e56a69d2f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fb7491c8190bcdb98d6cc003d9e |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:44 p.m.