Triple
T16180043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABS |
E392659
|
entity |
| Predicate | laterAdoptedIn |
P122018
|
FINISHED |
| Object | passenger vehicles |
—
|
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 vehicles | Statement: [ABS, laterAdoptedIn, passenger vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAdoptedIn Context triple: [ABS, laterAdoptedIn, passenger vehicles]
-
A.
laterAdoptedBy
Indicates that one entity is adopted by another entity at a later point in time, after some prior state or relationship has already been established.
-
B.
historicallyAdoptedBy
Indicates that something (such as a practice, policy, idea, or object) was used or taken up by an entity at some point in the past.
-
C.
originallyAdoptedAs
Indicates that an entity was first taken on, implemented, or accepted in a particular form, context, or role before any later changes or developments.
-
D.
adoptedAt
Indicates the time or date at which an adoption event took place.
-
E.
adoptedAfter
Indicates that one entity was adopted at a later time than another entity.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205b88b481908ecdd8d663dc668b |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.