Triple
T20626190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandy Row, Belfast |
E506822
|
entity |
| Predicate | hasParadingTradition |
P19423
|
FINISHED |
| Object | Orange Order parades |
—
|
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: Orange Order parades | Statement: [Sandy Row, Belfast, hasParadingTradition, Orange Order parades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParadingTradition Context triple: [Sandy Row, Belfast, hasParadingTradition, Orange Order parades]
-
A.
hasParadeFeature
Indicates that an entity includes, exhibits, or is characterized by a particular feature or element of a parade.
-
B.
hasTraditionIn
chosen
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
C.
hasParades
Indicates that an entity regularly holds or hosts parades as events or activities.
-
D.
hasWinningTradition
Indicates that an entity (such as a team or organization) is characterized by a consistent history of success or victories in its competitive activities.
-
E.
hasAthletesParade
Indicates that a group or organization holds or organizes a parade featuring its athletes.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abe576c081909231dc0d7304b9a9 |
completed | April 20, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:42 a.m.