Triple
T24801125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeep Active Drive Low |
E620524
|
entity |
| Predicate | usedOnGeneration |
P2367
|
FINISHED |
| Object | second-generation Jeep Compass (MP) |
—
|
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: second-generation Jeep Compass (MP) | Statement: [Jeep Active Drive Low, usedOnGeneration, second-generation Jeep Compass (MP)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnGeneration Context triple: [Jeep Active Drive Low, usedOnGeneration, second-generation Jeep Compass (MP)]
-
A.
appliedToGeneration
Indicates that an action, rule, or process is directed toward or used on a specific generation or age cohort.
-
B.
usedOn
chosen
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
C.
introducedInGeneration
Indicates that an entity first appeared or was originally introduced in a specified generation within a series or system.
-
D.
usedByGens
Indicates that something is utilized or employed by one or more generations (or generational groups).
-
E.
usedOnSpacecraftGeneration
Indicates that something is employed or applied in the process of designing, developing, or producing a generation of spacecraft.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f412aacd388190aa3cae919d6bdee2 |
completed | May 1, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:49 a.m.