Triple
T37604707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM P platform (Fiero) |
E935615
|
entity |
| Predicate | usedExclusivelyFor |
P43059
|
FINISHED |
| Object | Pontiac Fiero |
—
|
NE NERFINISHED |
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: Pontiac Fiero | Statement: [GM P platform (Fiero), usedExclusivelyFor, Pontiac Fiero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedExclusivelyFor Context triple: [GM P platform (Fiero), usedExclusivelyFor, Pontiac Fiero]
-
A.
exclusiveTo
chosen
Indicates that something is restricted or limited to a specific entity, group, or context and not shared with others.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
usedInternally
Indicates that something is utilized within an organization, system, or component itself rather than being exposed or provided for external use.
-
D.
providesExclusivity
Indicates that one entity grants another entity exclusive rights or access, preventing others from receiving the same benefit or opportunity.
-
E.
existsOnlyAs
Indicates that the subject exists solely in a particular form, state, or context specified by the object, and not in any other.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.