Triple
T34575709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol Singapore |
E887745
|
entity |
| Predicate | containsHeritageBuilding |
P163831
|
FINISHED |
| Object | Capitol Building |
—
|
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: Capitol Building | Statement: [Capitol Singapore, containsHeritageBuilding, Capitol Building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsHeritageBuilding Context triple: [Capitol Singapore, containsHeritageBuilding, Capitol Building]
-
A.
hasHeritageElements
chosen
Indicates that something contains or includes elements that are part of a cultural, historical, or natural heritage.
-
B.
hasHeritageFeature
Indicates that an entity possesses or includes a feature recognized as part of cultural, historical, or natural heritage.
-
C.
isPartOfHeritage
Indicates that something belongs to, contributes to, or is recognized as a component of a broader cultural, historical, or natural heritage.
-
D.
hasHeritageValueFor
Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
-
E.
hasHeritageUse
Indicates that something is used, managed, or valued in a way that relates to cultural, historical, or natural heritage.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00781b749c8190921c46e110cae0b0 |
completed | May 10, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_6a0077df3c8481909fabc9e84f5936e3 |
completed | May 10, 2026, 12:19 p.m. |
Created at: May 1, 2026, 2:03 a.m.