Triple
T30005145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Museum Fridericianum |
E762287
|
entity |
| Predicate | roleInDocumenta |
P199415
|
FINISHED |
| Object | central venue |
—
|
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: central venue | Statement: [Museum Fridericianum, roleInDocumenta, central venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDocumenta Context triple: [Museum Fridericianum, roleInDocumenta, central venue]
-
A.
documentsRole
Indicates that one entity serves to record, describe, or provide evidence of the role or function played by another entity.
-
B.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
C.
libraryRole
Indicates the specific function, responsibility, or position an entity holds within the context of a library.
-
D.
roleInMetadata
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
-
E.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
| PDg | Predicate description generation | batch_69ff38b8843c819097359a4d77e9d442 |
completed | May 9, 2026, 1:38 p.m. |
Created at: April 29, 2026, 6:42 p.m.