Triple
T28890608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sauron’s stronghold |
E732682
|
entity |
| Predicate | goalOfOccupant |
P165492
|
FINISHED |
| Object | domination of Middle-earth |
—
|
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: domination of Middle-earth | Statement: [Sauron’s stronghold, goalOfOccupant, domination of Middle-earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfOccupant Context triple: [Sauron’s stronghold, goalOfOccupant, domination of Middle-earth]
-
A.
fieldOfOccupant
Indicates the specific professional or academic field in which an occupant is engaged or associated.
-
B.
intendedOccupant
Indicates that one entity is designated or meant to be the occupant of another entity (such as a space, seat, or dwelling).
-
C.
jurisdictionOfOccupant
Indicates the legal authority or control that an occupant exercises over a place, property, or domain.
-
D.
occupationOf
Indicates that one entity holds or performs the job, role, or profession associated with another entity.
-
E.
regionServedByOccupant
Indicates that a particular region is served, covered, or attended to by a specified occupant (such as an organization, agent, or tenant).
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a75dfc88190b919126bcafd64c7 |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 7:54 a.m.