Triple
T36114965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota rally-raid programs |
E1044593
|
entity |
| Predicate | technologyTransferTo |
P107266
|
FINISHED |
| Object | Toyota production pickups |
—
|
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: Toyota production pickups | Statement: [Toyota rally-raid programs, technologyTransferTo, Toyota production pickups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyTransferTo Context triple: [Toyota rally-raid programs, technologyTransferTo, Toyota production pickups]
-
A.
technologyTransferFrom
Indicates that knowledge, methods, or technology are being transferred or shared from one entity to another.
-
B.
technologyTransmitted
chosen
Indicates that some form of technology is passed or transferred from one entity to another.
-
C.
hasTechnologyTransferOffice
Indicates that an entity possesses or is associated with a dedicated office or unit responsible for managing technology transfer activities.
-
D.
transferFeature
Indicates a relationship where a feature, attribute, or capability is moved or reassigned from one entity to another.
-
E.
acquiredTechnologyFrom
Indicates that one entity obtained or gained access to a technology from another entity.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.