Triple
T28067680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rover 800 |
E709298
|
entity |
| Predicate | engineeringCollaborationWith |
P38701
|
FINISHED |
| Object | Honda |
—
|
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: Honda | Statement: [Rover 800, engineeringCollaborationWith, Honda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineeringCollaborationWith Context triple: [Rover 800, engineeringCollaborationWith, Honda]
-
A.
collaborationOf
chosen
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
B.
platformCollaboration
Indicates a collaborative relationship where multiple entities work together or integrate their efforts on or through a shared platform.
-
C.
collaborativeWork
Indicates a relationship where two or more entities jointly contribute effort or resources toward a shared task, project, or goal.
-
D.
collaborationModel
Indicates the type or structure of cooperative interaction or joint work established between entities.
-
E.
collaborationAspect
Indicates a specific characteristic, dimension, or feature of how entities collaborate or work together.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6401cee508190a0dd02cb60d72f3b |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f637120c008190b2b5adf46f022e48 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:44 p.m.