Triple
T24904086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mecachrome |
E623655
|
entity |
| Predicate | preparedEnginesFor |
P59605
|
FINISHED |
| Object | Renault Formula 1 engines |
—
|
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: Renault Formula 1 engines | Statement: [Mecachrome, preparedEnginesFor, Renault Formula 1 engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preparedEnginesFor Context triple: [Mecachrome, preparedEnginesFor, Renault Formula 1 engines]
-
A.
preparedFor
chosen
Indicates that one entity has been made ready, equipped, or arranged in anticipation of use by or in connection with another entity.
-
B.
preparedBefore
Indicates that one entity was prepared or made ready at an earlier time than another entity.
-
C.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
D.
preparedAt
Indicates the time or place at which something was prepared or made ready.
-
E.
preparesWith
Indicates that one entity is used as a means, tool, or method by which another entity is prepared or made ready.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:27 a.m.