Triple
T6846538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roero |
E157908
|
entity |
| Predicate | DOCGStatusSince |
P19818
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Roero, DOCGStatusSince, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DOCGStatusSince Context triple: [Roero, DOCGStatusSince, 2004]
-
A.
DOCStatus
Indicates the current state or condition of a document within a defined process or lifecycle.
-
B.
hasDocumentationStatus
Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
-
C.
currentStatusSince
chosen
Indicates the point in time since which an entity has held its current status or state.
-
D.
DOCEstablished
Indicates that a document or organization was formally created, founded, or brought into official existence at a specific time or by a specific agent.
-
E.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d7cbe4488190b41ddf953f12f55f |
completed | March 27, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.