Triple
T12900502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNU ELPA |
E308598
|
entity |
| Predicate | curationLevel |
P107343
|
FINISHED |
| Object | curated |
—
|
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: curated | Statement: [GNU ELPA, curationLevel, curated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curationLevel Context triple: [GNU ELPA, curationLevel, curated]
-
A.
curationType
Indicates the specific manner or method by which something has been selected, organized, or managed within a curated collection or context.
-
B.
curationStatus
Indicates the current stage or condition of an item within a curation or review workflow (e.g., pending, approved, rejected, or in progress).
-
C.
curatedAt
Indicates the time or context at which an item was intentionally selected, organized, or assembled as part of a curated collection or set.
-
D.
curatedIn
Indicates that an entity has been intentionally selected, organized, or managed for inclusion within a particular collection, exhibition, or curated context.
-
E.
curatedFor
Indicates that something has been selectively organized, chosen, or tailored specifically to suit the needs, interests, or context of a particular target entity.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97180ee708190b60a3e58c42f764f |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:40 p.m.