Triple
T339701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oscan language |
E6805
|
entity |
| Predicate | wentExtinct |
P7427
|
FINISHED |
| Object | 1st century CE |
—
|
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: 1st century CE | Statement: [Oscan language, wentExtinct, 1st century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wentExtinct Context triple: [Oscan language, wentExtinct, 1st century CE]
-
A.
extinctionPeriod
chosen
Indicates the time span during which an entity ceases to exist or is considered extinct.
-
B.
extinctionReason
Indicates the cause or factor responsible for an entity’s extinction.
-
C.
hasExtinctBranch
Indicates that an entity has at least one branch, lineage, or subdivision that no longer exists (is extinct).
-
D.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
E.
containsFossilsOf
Indicates that one entity (typically a geological formation, rock, or sample) includes fossil remains or traces belonging to another entity (an organism or taxon).
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae4fcc08190bd4c2bf0149c8b50 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.