Triple
T32572447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibson Explorer |
E832550
|
entity |
| Predicate | marketReceptionAtLaunch |
P5170
|
FINISHED |
| Object | poor |
—
|
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: poor | Statement: [Gibson Explorer, marketReceptionAtLaunch, poor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketReceptionAtLaunch Context triple: [Gibson Explorer, marketReceptionAtLaunch, poor]
-
A.
marketReception
chosen
Indicates how a product, service, or work is received, evaluated, and responded to by the market or audience after its introduction.
-
B.
marketPositionAtRelease
Indicates the competitive standing or rank of an entity in its market at the time it is released.
-
C.
marketAdoption
Indicates the extent to which a product, service, or innovation has been accepted and used by its target market or customer base.
-
D.
marketDebut
Indicates the event or point in time when something (such as a product, service, or asset) is first introduced or made available on the market.
-
E.
receptionAtRelease
Indicates how something (such as a work, product, or event) was received or evaluated by others at the time it was first released.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:03 a.m.