Triple
T15668104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Continental R975 |
E377237
|
entity |
| Predicate | adaptedUse |
P2156
|
FINISHED |
| Object | armored vehicle powerplant |
—
|
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: armored vehicle powerplant | Statement: [Continental R975, adaptedUse, armored vehicle powerplant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptedUse Context triple: [Continental R975, adaptedUse, armored vehicle powerplant]
-
A.
usedInAdaptation
Indicates that something (such as a character, plot element, or work) is incorporated or appears within an adaptation of another original source.
-
B.
adaptedTo
Indicates that one entity has been modified, adjusted, or evolved to function effectively within the conditions, requirements, or characteristics defined by another entity.
-
C.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter another entity.
-
D.
adaptedAs
Indicates that one work, concept, or entity has been transformed or re-created into another form or medium based on the original.
-
E.
actualUse
chosen
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f1151548190a14607e762686cb1 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.