Triple
T3047720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gazoo Racing |
E83489
|
entity |
| Predicate | appliesTechnologyTo |
P1485
|
FINISHED |
| Object | Toyota production cars |
—
|
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: Toyota production cars | Statement: [Gazoo Racing, appliesTechnologyTo, Toyota production cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesTechnologyTo Context triple: [Gazoo Racing, appliesTechnologyTo, Toyota production cars]
-
A.
technologyPioneered
Indicates that an entity was the first or among the first to develop, introduce, or significantly advance a particular technology.
-
B.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
-
C.
developsTechnologyFor
Indicates that one entity creates, improves, or engineers technology specifically intended to be used by or to benefit another entity.
-
D.
associatedWithTechnology
chosen
Indicates a relationship where an entity is connected to, involved with, or utilizes a particular technology.
-
E.
upgradeTechnology
Indicates improving or replacing existing technology with a more advanced, efficient, or capable version.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bad11b48190a5bd01e91a320e14 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.