Triple
T9199339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGraw Tower |
E220795
|
entity |
| Predicate | hasChimesSchedule |
P86952
|
FINISHED |
| Object | daily chimes concerts |
—
|
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: daily chimes concerts | Statement: [McGraw Tower, hasChimesSchedule, daily chimes concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChimesSchedule Context triple: [McGraw Tower, hasChimesSchedule, daily chimes concerts]
-
A.
hasChimes
Indicates that one entity possesses or is equipped with chimes as a feature or component.
-
B.
chimes
Indicates that one entity produces a clear, resonant ringing sound, often as a signal or in response to a particular time or event.
-
C.
dateOfFirstChime
Indicates the calendar date on which something (such as a clock, bell, or chime mechanism) first produced a chime.
-
D.
hasAdministrationSchedule
Indicates that there is a defined plan or timetable specifying when and how an entity is to be administered or given.
-
E.
hasBells
Indicates that an entity possesses or is equipped with one or more bells.
- 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_69ca83e8e9248190862cf3e41693b310 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd881c5d48190bbc33fac71a1d849 |
completed | April 1, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6745c17881908df72443e0800068 |
completed | April 1, 2026, 12:31 a.m. |
Created at: March 30, 2026, 7:25 p.m.