Triple
T23013174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formula 3 teams |
E572960
|
entity |
| Predicate | usesEnginesFrom |
P131232
|
FINISHED |
| Object | series-specified engine suppliers |
—
|
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: series-specified engine suppliers | Statement: [Formula 3 teams, usesEnginesFrom, series-specified engine suppliers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEnginesFrom Context triple: [Formula 3 teams, usesEnginesFrom, series-specified engine suppliers]
-
A.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
-
B.
associatedWithEngine
chosen
Indicates a relationship in which something is connected, linked, or related to an engine, typically through use, function, or dependency.
-
C.
numberOfEngines
Indicates the quantity of engines associated with or used by an entity.
-
D.
engineUsedIn
Indicates that a particular engine is utilized as a component or power source within a specified system, device, or application.
-
E.
usesSpecEngine
Indicates that one entity employs or relies on a specific engine as its underlying mechanism or processing component.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e300008190bb12c6388a8b3280 |
completed | April 29, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.