Triple
T34669145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-Spec |
E890330
|
entity |
| Predicate | differenceFromB-Spec |
P179890
|
FINISHED |
| Object | player drives car directly |
—
|
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: player drives car directly | Statement: [A-Spec, differenceFromB-Spec, player drives car directly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differenceFromB-Spec Context triple: [A-Spec, differenceFromB-Spec, player drives car directly]
-
A.
differenceFromIFF
Indicates that two entities differ from each other if and only if a specified condition or set of criteria holds.
-
B.
designDifferenceFrom
Indicates a relationship where one design is distinguished from another by specific differing features, characteristics, or structure.
-
C.
isDifferenceOf
Indicates that one quantity or entity represents the result obtained by subtracting one specified quantity or entity from another.
-
D.
differenceDescription
Indicates a textual explanation that characterizes how two entities differ from each other.
-
E.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f728a1a0d081909e1b4465e7b88390 |
completed | May 3, 2026, 10:51 a.m. |
Created at: May 1, 2026, 2:05 a.m.