Triple
T20159110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberammergau |
E491655
|
entity |
| Predicate | passionPlayOrganizedBy |
P91582
|
FINISHED |
| Object | citizens of Oberammergau |
—
|
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: citizens of Oberammergau | Statement: [Oberammergau, passionPlayOrganizedBy, citizens of Oberammergau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passionPlayOrganizedBy Context triple: [Oberammergau, passionPlayOrganizedBy, citizens of Oberammergau]
-
A.
organizadoPor
Indicates that something is arranged, managed, or coordinated by a particular agent or entity.
-
B.
areOrganizedBy
chosen
Indicates that one entity is responsible for planning, coordinating, or managing the structure or execution of another entity or event.
-
C.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
-
D.
mayBeOrganizedBy
Indicates that an event, activity, or entity has the possibility of being organized or arranged by a particular agent or organization, without asserting that this organization definitely occurs.
-
E.
providedByOrganizer
Indicates that something (such as a resource, service, or information) is supplied or made available by the organizer.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667e27aa88190a326288b992ea274 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:34 p.m.