Triple
T33785039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dz.U. |
E865761
|
entity |
| Predicate | identifierElement |
P177371
|
FINISHED |
| Object | year |
—
|
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: year | Statement: [Dz.U., identifierElement, year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifierElement Context triple: [Dz.U., identifierElement, year]
-
A.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
B.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
-
C.
symbolElement
Indicates that one entity is a constituent element or component that makes up the other entity, which is treated as a symbol.
-
D.
identifiableBy
chosen
Indicates that one entity can be uniquely recognized, distinguished, or referenced by another entity (such as an identifier, attribute, or feature).
-
E.
identified
Indicates that one entity has recognized, named, or established the identity of another entity.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:45 a.m.