Triple
T4926357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grote Kerk, Haarlem |
E110585
|
entity |
| Predicate | organFamousFor |
P59510
|
FINISHED |
| Object | size and sound quality |
—
|
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: size and sound quality | Statement: [Grote Kerk, Haarlem, organFamousFor, size and sound quality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organFamousFor Context triple: [Grote Kerk, Haarlem, organFamousFor, size and sound quality]
-
A.
inscriptionFamousFor
Indicates that an inscription is widely recognized or notable specifically because of the referenced feature, event, content, or characteristic.
-
B.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
notableCulturalFigure
Indicates that a person holds significant influence or recognition within a culture’s arts, traditions, values, or public life.
-
D.
fatherNotableFor
Indicates that a person's father is recognized or distinguished for a particular achievement, role, or characteristic.
-
E.
famousForEvent
Indicates that an entity is widely known or recognized specifically because of a particular event.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70354bd081909291a43439f42ed3 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6d3806f881909c06687e9e57b67f |
completed | March 20, 2026, 3:52 p.m. |
Created at: March 20, 2026, 1:30 p.m.