Triple
T36546793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortal Men |
E901159
|
entity |
| Predicate | politicalEntities |
P46230
|
FINISHED |
| Object | Gondor |
—
|
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: Gondor | Statement: [Mortal Men, politicalEntities, Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalEntities Context triple: [Mortal Men, politicalEntities, Gondor]
-
A.
politicalEntity
Indicates that an entity functions as or is recognized as a political unit, organization, or actor within a political system.
-
B.
featuresPoliticalEntity
Indicates that something includes, presents, or prominently involves a political entity in its content or composition.
-
C.
politicalEntityWithin
chosen
Indicates that one political entity is geographically or administratively contained within another political entity.
-
D.
politicalEntityConstrained
Indicates that a political entity is subject to limitations, restrictions, or control imposed by another actor, rule, or condition.
-
E.
politicalEntityAtTime
Indicates that a political entity exists or holds a particular political status during a specified time 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: May 3, 2026, 4:11 p.m.