Triple
T9094579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Dumbarton |
E217982
|
entity |
| Predicate | statusOfFirstCreation |
P87135
|
FINISHED |
| Object | extinct |
—
|
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: extinct | Statement: [Earl of Dumbarton, statusOfFirstCreation, extinct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfFirstCreation Context triple: [Earl of Dumbarton, statusOfFirstCreation, extinct]
-
A.
createdStatus
Indicates that an entity has been newly created and is in its initial or just-established state within a system or process.
-
B.
classifiedStatusAtCreation
Indicates that an entity’s classification level or status (e.g., security or confidentiality classification) at the time it was created is being specified.
-
C.
firstCreatedUsing
Indicates that one entity was initially produced or brought into existence through the use, application, or involvement of another entity.
-
D.
hasCreation
Indicates a relationship where one entity is the creator or originator of another entity.
-
E.
firstCreatedAt
Indicates the time or date at which an entity was initially created for the first time.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc96b4a2e0819092f4eae8b1d21f33 |
completed | April 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:14 p.m.