Triple
T9106090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford BlueCruise |
E218480
|
entity |
| Predicate | operationalLimitation |
P99
|
FINISHED |
| Object | only on mapped sections of highways |
—
|
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: only on mapped sections of highways | Statement: [Ford BlueCruise, operationalLimitation, only on mapped sections of highways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalLimitation Context triple: [Ford BlueCruise, operationalLimitation, only on mapped sections of highways]
-
A.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
B.
reasonForPerformanceLimitation
Indicates that one factor serves as the cause or explanation for why a performance limitation occurs.
-
C.
showsLimitationOf
Indicates that one entity reveals, demonstrates, or makes apparent the limitations, weaknesses, or constraints of another entity.
-
D.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
E.
securityLimitation
Indicates a constraint, restriction, or boundary imposed for security purposes on what actions, access, or operations are allowed between entities.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca57286a88190b256d2461c5c0aed |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.