Triple
T14567552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Slate |
E341822
|
entity |
| Predicate | curationScope |
P78075
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [Main Slate, curationScope, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curationScope Context triple: [Main Slate, curationScope, global]
-
A.
curationType
Indicates the specific manner or method by which something has been selected, organized, or managed within a curated collection or context.
-
B.
curationLevel
Indicates the degree or extent to which something has been deliberately selected, organized, or refined by a curator or curatorial process.
-
C.
hasCuratorialScope
chosen
Indicates the specific thematic, temporal, geographic, or collection focus that defines the boundaries of an entity’s curatorial responsibility or activity.
-
D.
coCuratedWith
Indicates that two or more entities have been jointly curated or organized together as part of the same curation activity or process.
-
E.
curatedIn
Indicates that an entity has been intentionally selected, organized, or managed for inclusion within a particular collection, exhibition, or curated context.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb38d89fc819086709fd3607b835f |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.