Triple
T17518380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascension |
E426623
|
entity |
| Predicate | cloneStateIntroduced |
P127742
|
FINISHED |
| Object | Alpha |
—
|
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: Alpha | Statement: [Ascension, cloneStateIntroduced, Alpha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cloneStateIntroduced Context triple: [Ascension, cloneStateIntroduced, Alpha]
-
A.
introducedForState
Indicates that something was created, proposed, or brought forward specifically for use in or application to a particular state.
-
B.
classIntroduced
Indicates that a particular class (e.g., in a programming language or system) has been newly defined or made available within a given context or scope.
-
C.
alsoFromState
Indicates that two entities originate from, are associated with, or come from the same state or region.
-
D.
reintroducedFrom
Indicates that an entity has been brought back or restored from a specified prior source, context, or location after having been removed, lost, or discontinued.
-
E.
recognizedNewState
Indicates that an entity has formally acknowledged or accepted the existence or authority of a newly established state or political entity.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d0daa48190be69aff32b0324bc |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.