Triple
T33423140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford EXP |
E855895
|
entity |
| Predicate | notableTrim |
P25549
|
FINISHED |
| Object |
EXP Luxury
EXP Luxury was an upscale trim level of Ford's compact EXP sports coupe, featuring enhanced comfort and appearance options compared to the base model.
|
E2050581
|
NE 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: EXP Luxury | Statement: [Ford EXP, notableTrim, EXP Luxury]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: EXP Luxury Triple: [Ford EXP, notableTrim, EXP Luxury]
Generated description
EXP Luxury was an upscale trim level of Ford's compact EXP sports coupe, featuring enhanced comfort and appearance options compared to the base model.
Provenance (5 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e45ab2b0819096f00f6b9a1c03b5 |
completed | May 3, 2026, 5:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35814f624881909ea5e14783785d5e |
completed | June 19, 2026, 5:50 p.m. |
| NEDg | Description generation | batch_6a3581cb25a48190a378441d91cbb77c |
completed | June 19, 2026, 5:52 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a358263c5a08190afc50fc89f3d11db |
completed | June 19, 2026, 5:54 p.m. |
Created at: May 1, 2026, 1:36 a.m.