Triple
T33423404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granada GL |
E855902
|
entity |
| Predicate | higherEquipmentLevelThan |
P190026
|
FINISHED |
| Object | base Ford Granada trim |
—
|
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: base Ford Granada trim | Statement: [Granada GL, higherEquipmentLevelThan, base Ford Granada trim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherEquipmentLevelThan Context triple: [Granada GL, higherEquipmentLevelThan, base Ford Granada trim]
-
A.
typicalEquipmentLevel
Indicates the usual or standard amount or quality of equipment associated with an entity or situation.
-
B.
hasUpgradeLevel
chosen
Indicates that an entity possesses a specific upgrade stage or level within a progression or enhancement system.
-
C.
hasHigherListingRequirementsThan
Indicates that one entity is subject to stricter or more demanding listing requirements than another entity.
-
D.
levelRequirement
Indicates that one entity specifies the minimum level or threshold another entity must meet in order for an action, access, or condition to be valid.
-
E.
higherRankHas
Indicates that one entity holds a higher rank or hierarchical position than another entity.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 1, 2026, 1:36 a.m.