Triple
T3604682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netherlands Open Air Museum |
E76340
|
entity |
| Predicate | hasDemonstration |
P49902
|
FINISHED |
| Object | cheese making |
—
|
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: cheese making | Statement: [Netherlands Open Air Museum, hasDemonstration, cheese making]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDemonstration Context triple: [Netherlands Open Air Museum, hasDemonstration, cheese making]
-
A.
hasTypeOfDemonstration
Indicates that an event or action is characterized by a specific kind or category of demonstration.
-
B.
demonstratedOn
Indicates that an action, behavior, or property is shown, illustrated, or proven using a particular entity as the example or subject.
-
C.
hasTechnologyDemonstration
Indicates that an entity includes, features, or is associated with a demonstration of a particular technology or technological capability.
-
D.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
E.
demonstratedAt
Indicates that an action, behavior, or capability was shown or exhibited at a particular event, location, or point in time.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1e07bc481908d9fce18d36d8e0d |
completed | March 8, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:22 p.m.