Triple
T36080730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Narnians |
E1043637
|
entity |
| Predicate | statusDuringTelmarineRule |
P200612
|
FINISHED |
| Object | driven into hiding |
—
|
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: driven into hiding | Statement: [Old Narnians, statusDuringTelmarineRule, driven into hiding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringTelmarineRule Context triple: [Old Narnians, statusDuringTelmarineRule, driven into hiding]
-
A.
laterUnderRuleOf
Indicates that one entity came to be governed or ruled by another entity at a later point in time.
-
B.
regionAfterHisRule
Indicates that a region is in the state or condition it has after the end of his period of rule or governance.
-
C.
underRule
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another entity.
-
D.
laysDownRulingOn
Indicates that an authority formally issues or establishes a decision, judgment, or rule concerning a particular matter or case.
-
E.
legendaryRule
Indicates that an entity holds a unique, mythic or legendary status that governs or constrains how it can exist or interact within a given system or context.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
| PDg | Predicate description generation | batch_69ff9b19f254819099bb9c034d2b399b |
completed | May 9, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:08 p.m.