Triple
T23206666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States (fictional setting) |
E580475
|
entity |
| Predicate | differenceType |
P17124
|
FINISHED |
| Object | may alter historical events |
—
|
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: may alter historical events | Statement: [United States (fictional setting), differenceType, may alter historical events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differenceType Context triple: [United States (fictional setting), differenceType, may alter historical events]
-
A.
differenceDescription
Indicates a textual explanation that characterizes how two entities differ from each other.
-
B.
deltaType
chosen
Indicates a classification of the kind or category of change (difference) that has occurred between two related states or versions.
-
C.
sequenceDifferenceType
Indicates the type or nature of the difference between two related sequences.
-
D.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
E.
pointDifference
Indicates the numerical difference in points or scores between two compared entities.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907cd62c8190afee1e963b170727 |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.