Triple
T23517926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volvo P1 platform |
E574419
|
entity |
| Predicate | sharesCoreUnderpinningsWith |
P13870
|
FINISHED |
| Object | Ford C1 platform |
—
|
NE NERFINISHED |
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: Ford C1 platform | Statement: [Volvo P1 platform, sharesCoreUnderpinningsWith, Ford C1 platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCoreUnderpinningsWith Context triple: [Volvo P1 platform, sharesCoreUnderpinningsWith, Ford C1 platform]
-
A.
sharesMantleWith
Indicates that two entities occupy or are associated with the same mantle, layer, or mantle-like structure.
-
B.
sharesValuesWith
Indicates that two entities hold similar or compatible beliefs, principles, or priorities.
-
C.
sharesComplexWith
Indicates that two entities are components of, or co-residents within, the same larger complex or composite structure.
-
D.
sharesAlignmentWith
Indicates that two entities have the same or sufficiently similar alignment, orientation, or stance according to a defined alignment system.
-
E.
sharesComponentsWith
chosen
Indicates that two entities have one or more structural or functional components in common.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa83c538819096bc548e3e0ddbd0 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:08 p.m.