Triple
T16805868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stevenskerk |
E408479
|
entity |
| Predicate | hasOrganBy |
P124916
|
FINISHED |
| Object | various organ builders over centuries |
—
|
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: various organ builders over centuries | Statement: [Stevenskerk, hasOrganBy, various organ builders over centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrganBy Context triple: [Stevenskerk, hasOrganBy, various organ builders over centuries]
-
A.
hasOrganizationFor
Indicates that one entity possesses, is associated with, or is responsible for a particular organization in relation to some context or purpose.
-
B.
hadOrganization
Indicates that an entity was affiliated with, employed by, or otherwise formally associated with a particular organization during some period of time.
-
C.
hasMemberOrganizationsIn
Indicates that an entity includes or comprises member organizations that are located in or associated with a specified place or region.
-
D.
hadOrgan
Indicates that an entity previously possessed or contained a specific organ as part of its body.
-
E.
имеетОрган
Indicates that one entity possesses or contains a specific organ as a part of its body.
- 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_69e3b2cc25dc81909443b2c83155267a |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:22 a.m.