Triple
T12936881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theosophical Society |
E309533
|
entity |
| Predicate | relocatedHeadquartersYear |
P12036
|
FINISHED |
| Object | 1882 |
—
|
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: 1882 | Statement: [Theosophical Society, relocatedHeadquartersYear, 1882]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocatedHeadquartersYear Context triple: [Theosophical Society, relocatedHeadquartersYear, 1882]
-
A.
headquartersMovedOn
chosen
Indicates that the location of an entity’s headquarters changed on a specific date or point in time.
-
B.
headquartersCompletionYear
Indicates the year in which an organization's headquarters building was completed.
-
C.
usedAsHeadquartersDuringYear
Indicates that a location served as the main headquarters for an entity during a specified year.
-
D.
movedHeadquartersFrom
Indicates that an entity relocated its main headquarters from one specified place to another.
-
E.
movedHeadquartersAfter
Indicates that one entity relocated its main headquarters to a new place or organization after a point in time or event associated with another entity.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.