Triple
T4266516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perth Concert Hall |
E96837
|
entity |
| Predicate | hasPipeOrgan |
P55079
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Perth Concert Hall, hasPipeOrgan, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPipeOrgan Context triple: [Perth Concert Hall, hasPipeOrgan, true]
-
A.
hasOrganPlayer
Indicates that an entity has another entity serving as its organ player.
-
B.
numberOfOrganPipes
Indicates the quantitative relationship specifying how many organ pipes are associated with a given organ or organ-related entity.
-
C.
hasOldestPlayableOrgan
Indicates that the subject possesses or is associated with the oldest playable organ.
-
D.
hasOrchestraPit
Indicates that a venue or performance space includes a designated orchestra pit area for musicians.
-
E.
hasCarillonSince
Indicates that an entity has possessed or been equipped with a carillon continuously from a specified point in time.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fcc383c81908e17da7cbc86a630 |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:07 p.m.