Triple
T16797947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Mary’s Basilica (Kraków) |
E408281
|
entity |
| Predicate | trumpetCallDirection |
P124670
|
FINISHED |
| Object | played towards the four corners of the world |
—
|
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: played towards the four corners of the world | Statement: [St. Mary’s Basilica (Kraków), trumpetCallDirection, played towards the four corners of the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trumpetCallDirection Context triple: [St. Mary’s Basilica (Kraków), trumpetCallDirection, played towards the four corners of the world]
-
A.
terminusDirection
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
B.
connectionDirection
Indicates the directional flow or orientation of a connection from one entity to another.
-
C.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
D.
isDirection
Indicates that one entity specifies or represents the orientation or course along which another entity moves, points, or is aligned.
-
E.
communicationDirection
Indicates the directional flow of a communication act, specifying who is sending information and who is receiving it.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2ab08e8819097072a23c4a62392 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319d0fdb8819088425bd82431640f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:22 a.m.