Triple
T34505864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mustang EcoBoost (S550) |
E885882
|
entity |
| Predicate | availablePackage |
P73918
|
FINISHED |
| Object | EcoBoost Performance Package |
—
|
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: EcoBoost Performance Package | Statement: [Mustang EcoBoost (S550), availablePackage, EcoBoost Performance Package]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availablePackage Context triple: [Mustang EcoBoost (S550), availablePackage, EcoBoost Performance Package]
-
A.
availableWith
Indicates that one entity can be obtained, accessed, or used in conjunction with another entity.
-
B.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
C.
availableFor
Indicates that one entity can be used, accessed, or allocated for the benefit, purpose, or use of another entity.
-
D.
mayBeAvailableIn
Indicates that an entity has the potential to be obtainable, accessible, or present within a specified context, location, or medium.
-
E.
hasPerformancePackage
chosen
Indicates that an entity is equipped with or associated with a specific performance-enhancing package or upgrade.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.