Triple
T216003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney Opera House |
E4105
|
entity |
| Predicate | annualPerformances |
P9704
|
FINISHED |
| Object | over 1500 |
—
|
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: over 1500 | Statement: [Sydney Opera House, annualPerformances, over 1500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annualPerformances Context triple: [Sydney Opera House, annualPerformances, over 1500]
-
A.
annualEvent
Indicates that an event occurs once every year on a recurring basis.
-
B.
annualFrom
Indicates that something recurs or is calculated on a yearly basis starting from a specified point in time.
-
C.
livePerformanceStapleFor
Indicates that something (such as a song or piece) is regularly and prominently featured in another entity’s live performances.
-
D.
firstPerformance
Indicates that an entity marks the initial or debut performance of another entity, such as a work, artist, or production.
-
E.
completionAnniversary
Indicates the date or event marking the anniversary of when something was originally completed.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b52190481908f299d26122bafd2 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25dcba5148190ab80fd14c7cf4bb4 |
completed | Feb. 28, 2026, 3:15 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.