Triple
T33493942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Symphony Orchestra |
E857813
|
entity |
| Predicate | formerResidency |
P4907
|
FINISHED |
| Object | Victoria Concert Hall |
—
|
NE NERFINISHED |
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: Victoria Concert Hall | Statement: [Singapore Symphony Orchestra, formerResidency, Victoria Concert Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerResidency Context triple: [Singapore Symphony Orchestra, formerResidency, Victoria Concert Hall]
-
A.
formerResidenceOf
chosen
Indicates that a location was once the place where a person or entity lived or was based, but is no longer their current residence.
-
B.
succeededByResidence
Indicates that one residence directly follows and replaces another as the primary place of dwelling for an entity.
-
C.
hasNearbyFormerResidenceOf
Indicates that one entity is located near a place that used to be the residence of another entity.
-
D.
residencyAt
Indicates that an entity lives or has an established residence at a particular location or address.
-
E.
formerCity
Indicates that an entity was once recognized as a city but no longer holds that status.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: May 1, 2026, 1:38 a.m.