Triple
T33045201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Williams Racing Cars |
E845574
|
entity |
| Predicate | hasEntrantRole |
P192073
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Frank Williams Racing Cars, hasEntrantRole, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntrantRole Context triple: [Frank Williams Racing Cars, hasEntrantRole, yes]
-
A.
hasEntranceRole
Indicates that an entity participates in an entrance or access point with a specific functional role or capacity.
-
B.
hasEnsembleRoleWith
Indicates that two or more entities share a collaborative or joint role within the same ensemble, group, or collective context.
-
C.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
-
D.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
E.
hasEarlyRoleFor
Indicates that one entity holds or performs an initial or early-stage role in relation to another entity or process.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 1, 2026, 1:24 a.m.