Triple
T33796237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James the Red Engine |
E866080
|
entity |
| Predicate | canPull |
P177712
|
FINISHED |
| Object | passenger trains |
—
|
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: passenger trains | Statement: [James the Red Engine, canPull, passenger trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canPull Context triple: [James the Red Engine, canPull, passenger trains]
-
A.
canCollect
Indicates that one entity has the ability or permission to gather, receive, or take possession of another entity.
-
B.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
-
C.
canRetrieve
Indicates that one entity has the ability or permission to retrieve or fetch another entity or resource.
-
D.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
E.
canTry
Indicates that an entity has the possibility or permission to attempt performing a particular action or achieving a certain outcome.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:46 a.m.