Triple
T28067581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rover 200 |
E709296
|
entity |
| Predicate | platformPartner |
P167345
|
FINISHED |
| Object | Honda Ballade |
E91713
|
NE 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: Honda Ballade | Statement: [Rover 200, platformPartner, Honda Ballade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformPartner Context triple: [Rover 200, platformPartner, Honda Ballade]
-
A.
technologyPartner
Indicates a collaborative relationship where one entity provides technological expertise, products, or services to support or co-develop another entity’s solutions or operations.
-
B.
launchPartner
Indicates that one entity collaborates closely with another as a primary partner during the initial launch or rollout of a product, service, or initiative.
-
C.
segmentPartner
Indicates a partnership relationship between entities within a specific segment, context, or category.
-
D.
partnerStudio
Indicates that one entity serves as a partner studio associated with, collaborating with, or officially linked to another entity.
-
E.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
- F. None of above. chosen
Provenance (5 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a15b8cad0b4819080a62b6933717e9f |
completed | May 26, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 27, 2026, 8:43 p.m.