Triple
T24861937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrysler ZJ platform |
E622175
|
entity |
| Predicate | notableEngineCompatibility |
P4856
|
FINISHED |
| Object | 4.0L AMC inline-six engine |
—
|
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: 4.0L AMC inline-six engine | Statement: [Chrysler ZJ platform, notableEngineCompatibility, 4.0L AMC inline-six engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEngineCompatibility Context triple: [Chrysler ZJ platform, notableEngineCompatibility, 4.0L AMC inline-six engine]
-
A.
notableGameSupport
Indicates that an entity is recognized for providing significant support or contribution to a particular game.
-
B.
hasSoftwareCompatibilityWith
Indicates that one software system can operate correctly and effectively with another software system, without conflicts or required modifications.
-
C.
notableEngineType
chosen
Indicates that an entity is particularly recognized for using or being associated with a specific type of engine.
-
D.
notableSupport
Indicates that one entity provides significant, recognized backing, endorsement, or assistance to another.
-
E.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 18, 2026, 5:22 a.m.