Triple
T11909146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S7 Stock |
E283347
|
entity |
| Predicate | configurationDifferenceFrom |
P74132
|
FINISHED |
| Object | S8 Stock has 8 cars while S7 has 7 cars |
—
|
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: S8 Stock has 8 cars while S7 has 7 cars | Statement: [S7 Stock, configurationDifferenceFrom, S8 Stock has 8 cars while S7 has 7 cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationDifferenceFrom Context triple: [S7 Stock, configurationDifferenceFrom, S8 Stock has 8 cars while S7 has 7 cars]
-
A.
differenceFromStates
Indicates that one state or condition is distinct from, or deviates in some way from, another state or condition.
-
B.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
C.
formsDeltaWith
Indicates that one entity combines or interacts with another to produce a change or difference (a “delta”) between states, values, or conditions.
-
D.
adaptationDifference
Indicates a difference or change in how two entities adapt or have adapted relative to each other.
-
E.
differenceDescription
chosen
Indicates a textual explanation that characterizes how two entities differ from each other.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5278eb081909a7ecfe38beeeda9 |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.