Triple
T38620480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Affliction |
E936851
|
entity |
| Predicate | isUpdateType |
P191296
|
FINISHED |
| Object | major expansion |
—
|
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: major expansion | Statement: [Affliction, isUpdateType, major expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUpdateType Context triple: [Affliction, isUpdateType, major expansion]
-
A.
isUpdateFor
Indicates that one entity serves as a newer or modified version that replaces or revises another entity.
-
B.
isUpdated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
-
C.
updatesType
Indicates that one entity modifies, revises, or replaces the type or classification of another entity.
-
D.
isUpdatedWhen
Indicates that one entity undergoes a change or refresh whenever another specified entity is modified or updated.
-
E.
isUpdatedThrough
Indicates that one entity’s state or content is modified or brought up to date as a result of a process, action, or interaction involving another 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.