Triple
T30537935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln ActiveGlide |
E777198
|
entity |
| Predicate | controlScope |
P79851
|
FINISHED |
| Object | steering |
—
|
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: steering | Statement: [Lincoln ActiveGlide, controlScope, steering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlScope Context triple: [Lincoln ActiveGlide, controlScope, steering]
-
A.
controlRange
Indicates the spatial or contextual extent within which an entity can exert control or influence over another entity or process.
-
B.
controlContext
Indicates that one entity governs, constrains, or determines the conditions under which another entity operates or is interpreted.
-
C.
controlPerspective
Indicates that one entity determines, influences, or manages the viewpoint or frame of reference through which another entity perceives or represents something.
-
D.
scopeOfControl
chosen
Indicates the extent or range within which an entity has authority, influence, or control over another entity or set of entities.
-
E.
controlStand
Indicates that one entity manages, directs, or regulates the operation or behavior of another entity or system.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 29, 2026, 8:19 p.m.