Triple
T19057879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell X-1A |
E466445
|
entity |
| Predicate | designedToInvestigate |
P134931
|
FINISHED |
| Object | transonic flight |
—
|
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: transonic flight | Statement: [Bell X-1A, designedToInvestigate, transonic flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToInvestigate Context triple: [Bell X-1A, designedToInvestigate, transonic flight]
-
A.
areInvestigatedFor
Indicates that one or more entities are the subject of an investigation concerning a particular issue, incident, or alleged wrongdoing.
-
B.
investigatesAt
Indicates that an entity conducts an investigation or research activity at a specific location or institution.
-
C.
containsInvestigationOf
Indicates that one entity includes or encompasses an investigation or inquiry concerning another entity.
-
D.
investigate
Indicates that one entity systematically examines, studies, or inquires into another entity or situation to uncover facts or gain understanding.
-
E.
investigatedFor
Indicates that an entity is the subject of an investigation concerning a suspected involvement in another entity (typically a crime, incident, or wrongdoing).
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc0742288190a594be859184841a |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4c0fc3c4c8190abbfe06e1bd3325c |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 12:03 p.m.