Triple
T33029002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | comp.lang.c |
E845113
|
entity |
| Predicate | creationEra |
P120335
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [comp.lang.c, creationEra, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creationEra Context triple: [comp.lang.c, creationEra, 1980s]
-
A.
creatorEra
Indicates the historical period or era during which the creator of an entity was active or produced the entity.
-
B.
historicalEraRecreated
Indicates that a past historical era has been reconstructed or simulated, typically for representation, study, or experiential purposes.
-
C.
livedInEra
Indicates that an entity existed or was active during a particular historical era or time period.
-
D.
introductionEra
Indicates the historical period or era during which something was first introduced or came into use.
-
E.
associatedProductionEra
chosen
Indicates a relationship where something is linked to the specific time period or era during which it was produced or created.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: May 1, 2026, 1:24 a.m.