Triple
T3769157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orizzonti |
E82753
|
entity |
| Predicate | curationFocus |
P31647
|
FINISHED |
| Object | formal experimentation |
—
|
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: formal experimentation | Statement: [Orizzonti, curationFocus, formal experimentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curationFocus Context triple: [Orizzonti, curationFocus, formal experimentation]
-
A.
curationType
Indicates the specific manner or method by which something has been selected, organized, or managed within a curated collection or context.
-
B.
curatorialContext
Indicates the relationship by which an entity is situated within, shaped by, or interpreted through a particular curatorial framework, selection, or presentation context.
-
C.
curatedBy
Indicates that something has been selectively organized, managed, or assembled by a particular agent or entity.
-
D.
curatedAt
Indicates the time or context at which an item was intentionally selected, organized, or assembled as part of a curated collection or set.
-
E.
focusType
chosen
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc2d4b848190bf63fb3ed5d3b2d9 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.