Triple
T3943149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Église Saint-Thomas de Strasbourg |
E92081
|
entity |
| Predicate | hasOrganTradition |
P1186
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Église Saint-Thomas de Strasbourg, hasOrganTradition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrganTradition Context triple: [Église Saint-Thomas de Strasbourg, hasOrganTradition, yes]
-
A.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
B.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
C.
hasRiteOrTradition
chosen
Indicates that an entity is associated with, practices, or observes a particular rite, ritual, or tradition.
-
D.
traditionAscribes
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
E.
traditionsMaintainedBy
Indicates that certain traditions are preserved, upheld, or continued in practice by a particular entity.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.