Triple
T3691620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota T100 |
E78355
|
entity |
| Predicate | platformRole |
P49775
|
FINISHED |
| Object | predecessor platform to Toyota Tundra’s full-size development |
—
|
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: predecessor platform to Toyota Tundra’s full-size development | Statement: [Toyota T100, platformRole, predecessor platform to Toyota Tundra’s full-size development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformRole Context triple: [Toyota T100, platformRole, predecessor platform to Toyota Tundra’s full-size development]
-
A.
technologyRole
Indicates the functional role or purpose that a technology plays within a system, process, or context.
-
B.
systemRole
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
C.
hardwareRole
Indicates the functional role or purpose that a piece of hardware serves within a system or configuration.
-
D.
configurationRole
Indicates the role or function an entity assumes within a particular configuration or setup.
-
E.
platformStrategy
Indicates a relationship where an entity defines or employs an overarching plan for building, managing, or leveraging a platform to create and capture value among its participants.
- F. None of above. chosen
Provenance (4 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4e783a88190b2837a68b8723a25 |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:26 p.m.