Triple
T36548777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tower of Sorcery |
E901200
|
entity |
| Predicate | formerlyFunctionedAs |
P202627
|
FINISHED |
| Object | Gondorian watch-tower |
—
|
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: Gondorian watch-tower | Statement: [Tower of Sorcery, formerlyFunctionedAs, Gondorian watch-tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyFunctionedAs Context triple: [Tower of Sorcery, formerlyFunctionedAs, Gondorian watch-tower]
-
A.
formerName
Indicates that an entity was previously known by a different name in the past.
-
B.
formerlyKnownLocationAs
Indicates that an entity was previously known or referred to by a different location name or designation.
-
C.
formerlyUsedBy
Indicates that an entity was used by another entity in the past but is no longer in use by that entity.
-
D.
functionedBefore
Indicates that one entity was operational or in working order at an earlier time than another entity.
-
E.
formerlyLocatedOn
Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00a22e32f481909b6006c5b1cdefd3 |
completed | May 10, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a00a1bd9c908190b4aa17a61f48126f |
completed | May 10, 2026, 3:18 p.m. |
| PDg | Predicate description generation | batch_6a00a22d837081909f19d1078c4fedad |
completed | May 10, 2026, 3:20 p.m. |
Created at: May 3, 2026, 4:11 p.m.