Triple
T6720581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Macquarie |
E153382
|
entity |
| Predicate | hasSiteUseAfterDemolition |
P43161
|
FINISHED |
| Object | construction site for the Sydney Opera House |
—
|
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: construction site for the Sydney Opera House | Statement: [Fort Macquarie, hasSiteUseAfterDemolition, construction site for the Sydney Opera House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiteUseAfterDemolition Context triple: [Fort Macquarie, hasSiteUseAfterDemolition, construction site for the Sydney Opera House]
-
A.
siteUseAfterDemolition
chosen
Indicates the subsequent use or function assigned to a site following the demolition of its previous structures.
-
B.
demolishedAfter
Indicates that one entity was demolished at a point in time later than the demolition of another entity.
-
C.
dateOfDemolition
Indicates the specific date on which a structure or object was demolished.
-
D.
demolishedAfterEvent
Indicates that one entity (typically a structure) was demolished after the occurrence of a specified event.
-
E.
hasSiteUse
Indicates that a site is used or designated for a particular function, activity, or purpose.
- 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d137084881908e04ee6b2bd45585 |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.