Triple
T33856346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edith |
E867785
|
entity |
| Predicate | plansDisruptedBy |
P178384
|
FINISHED |
| Object | Roger moving back home |
—
|
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: Roger moving back home | Statement: [Edith, plansDisruptedBy, Roger moving back home]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plansDisruptedBy Context triple: [Edith, plansDisruptedBy, Roger moving back home]
-
A.
causedTransportDisruption
Indicates that one entity was the cause of a disruption or interruption to the normal operation of a transport system or service.
-
B.
transportationPlanned
Indicates that an arrangement has been made for someone or something to be transported from one place to another.
-
C.
disruptedIn
Indicates that a normal process, function, or state is interrupted, impaired, or thrown into disorder within the specified context.
-
D.
plannedTransit
Indicates that a transit or trip has been scheduled or arranged to occur, but has not yet taken place.
-
E.
plannedDisplacement
Indicates a deliberate, pre-arranged movement or relocation of an entity from one place or state to another.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:47 a.m.