Triple
T13969317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greg Page |
E336010
|
entity |
| Predicate | injuryConsequence |
P23450
|
FINISHED |
| Object | partial paralysis |
—
|
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: partial paralysis | Statement: [Greg Page, injuryConsequence, partial paralysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: injuryConsequence Context triple: [Greg Page, injuryConsequence, partial paralysis]
-
A.
causeOfInjury
Indicates that one entity is the source or reason that another entity sustained an injury.
-
B.
injuryType
chosen
Indicates the specific kind or category of injury associated with an entity or event.
-
C.
consequenceOfCollision
Indicates that one event, state, or condition occurs as a direct result of a collision between entities.
-
D.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
E.
damageAssociatedWith
Indicates a relationship where one entity is linked to causing, contributing to, or being responsible for damage affecting another entity.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e8daeac8190aadd4b3b60222482 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.