Triple
T33675818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford T6 platform |
E862755
|
entity |
| Predicate | designGoals |
P6636
|
FINISHED |
| Object | shared global architecture |
—
|
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: shared global architecture | Statement: [Ford T6 platform, designGoals, shared global architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designGoals Context triple: [Ford T6 platform, designGoals, shared global architecture]
-
A.
overallDesignGoal
Indicates that one entity specifies or represents the primary design objective or guiding design intent for another entity.
-
B.
lifetimeDesignGoal
Indicates a design objective or target that is intended to be maintained or achieved over the entire lifetime of the system or product.
-
C.
engineeringGoal
Indicates that an entity has a specific engineering-related objective, target, or desired outcome it is intended to achieve or support.
-
D.
designCriteria
Indicates the standards, requirements, or constraints that guide how something should be planned, structured, or created.
-
E.
goals
chosen
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 1, 2026, 1:43 a.m.