Triple
T37315691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Osgiliath (War of the Ring) |
E926325
|
entity |
| Predicate | takesPlaceInRealm |
P84795
|
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: [Battle of Osgiliath (War of the Ring), takesPlaceInRealm, Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesPlaceInRealm Context triple: [Battle of Osgiliath (War of the Ring), takesPlaceInRealm, Gondor]
-
A.
residesInRealm
Indicates that an entity lives or exists within a particular realm or domain.
-
B.
realm
Indicates that one entity is a domain, sphere of influence, or area of control associated with another entity.
-
C.
realmWithin
Indicates that one realm or domain is contained inside, or exists as a subset of, another realm or domain.
-
D.
takesPlaceInRegion
chosen
Indicates that an event or occurrence happens within the boundaries of a specified geographic or administrative region.
-
E.
realmBecame
Indicates that one realm transformed into, or came to be recognized as, another realm at a particular point in time.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:16 p.m.