Triple
T34294418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Mustang Boss 429 |
E879982
|
entity |
| Predicate | conversionContractor |
P50446
|
FINISHED |
| Object | Kar Kraft |
—
|
NE NERFINISHED |
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: Kar Kraft | Statement: [Ford Mustang Boss 429, conversionContractor, Kar Kraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionContractor Context triple: [Ford Mustang Boss 429, conversionContractor, Kar Kraft]
-
A.
conversionDetails
Indicates the specific parameters, conditions, and outcomes associated with transforming one entity, state, or value into another.
-
B.
conversionTarget
Indicates that one entity serves as the intended outcome, goal, or result that another entity is meant to be converted or transformed into.
-
C.
conversionProgram
Indicates a program or process that transforms something from one form, state, or type into another.
-
D.
typeOfContractor
chosen
Indicates the specific category or role of a contractor in relation to a given entity or project.
-
E.
conversionOfferedIn
Indicates that an opportunity to convert (e.g., change status, format, or type) is made available within or through a specified context, channel, or environment.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 1:57 a.m.