Triple
T13924914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Government House, Brisbane |
E334838
|
entity |
| Predicate | governorResidenceFrom |
P39651
|
FINISHED |
| Object | 1862 |
—
|
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: 1862 | Statement: [Old Government House, Brisbane, governorResidenceFrom, 1862]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governorResidenceFrom Context triple: [Old Government House, Brisbane, governorResidenceFrom, 1862]
-
A.
governorResidenceFor
Indicates the official residence associated with or designated for a particular governor.
-
B.
governorResidenceSince
chosen
Indicates the time point or date from which a particular governor has been residing at a specified official residence.
-
C.
stateGovernorResidenceLocatedIn
Indicates that the official residence of a state governor is located within a specified geographic or political area.
-
D.
governorBasedIn
Indicates that a governor carries out their official duties or has their primary office located in a specified place.
-
E.
governorResidenceUntil
Indicates that a specified location served as the official residence of a governor up to a particular time or date.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa6cd9881908f652538f4613f37 |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.