Triple
T25654472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halla |
E643193
|
entity |
| Predicate | hasRulerInFiction |
P159173
|
FINISHED |
| Object | King of Halla |
—
|
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: King of Halla | Statement: [Halla, hasRulerInFiction, King of Halla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulerInFiction Context triple: [Halla, hasRulerInFiction, King of Halla]
-
A.
hasRankInFiction
Indicates that a fictional character or entity holds a specific rank, title, or hierarchical position within a fictional context or universe.
-
B.
hasControllerInFiction
Indicates that an entity is under the control or direction of a specified controller within a fictional context or narrative.
-
C.
hasRulerInGenesisNarrative
Indicates that one entity serves as the ruler or governing authority over another entity within the context of the Genesis narrative.
-
D.
hasFeatureInFiction
Indicates that a fictional work includes or portrays a particular feature, trait, or characteristic.
-
E.
hasRelativeInFiction
Indicates that one entity has a relative or family member who appears as a character within a fictional work associated with the other 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fae906108190af97edeac20f8140 |
completed | May 2, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 6:31 p.m.