Triple
T34079234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Select Plus |
E873986
|
entity |
| Predicate | statusBasis |
P199582
|
FINISHED |
| Object | annual Amtrak travel activity |
—
|
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: annual Amtrak travel activity | Statement: [Select Plus, statusBasis, annual Amtrak travel activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusBasis Context triple: [Select Plus, statusBasis, annual Amtrak travel activity]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
C.
statusQualifier
Indicates a modifier that refines or specifies the exact nature, condition, or context of a given status.
-
D.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
E.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
- F. None of above. chosen
Provenance (4 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69ff46aefe248190a80d898df6ef1340 |
completed | May 9, 2026, 2:37 p.m. |
Created at: May 1, 2026, 1:52 a.m.