Triple
T4047787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Mary’s Basilica |
E84108
|
entity |
| Predicate | trumpetCallPlayedFrom |
P14719
|
FINISHED |
| Object | higher northern tower |
—
|
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: higher northern tower | Statement: [St. Mary’s Basilica, trumpetCallPlayedFrom, higher northern tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trumpetCallPlayedFrom Context triple: [St. Mary’s Basilica, trumpetCallPlayedFrom, higher northern tower]
-
A.
hasPrincipalTrumpet
Indicates that one entity serves as the principal (lead) trumpet player for another entity, such as an orchestra or ensemble.
-
B.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
-
C.
hasPrincipalTimpanist
Indicates that an entity (such as an orchestra) has a specific person serving as its principal timpanist.
-
D.
playedFrom
chosen
Indicates that an action of playing (such as media playback or a performance) originated from a particular source or starting point.
-
E.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.