Triple
T8141789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medallion Qualification Miles |
E190114
|
entity |
| Predicate | statusDetermines |
P80906
|
FINISHED |
| Object | Silver Medallion status |
—
|
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: Silver Medallion status | Statement: [Medallion Qualification Miles, statusDetermines, Silver Medallion status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDetermines Context triple: [Medallion Qualification Miles, statusDetermines, Silver Medallion status]
-
A.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
B.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
C.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
D.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
-
E.
valuationStatus
Indicates the current state or condition of an entity’s assessed value within a valuation process (e.g., pending, active, finalized, or invalid).
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4442299881909db56f7475cbb99a |
completed | March 31, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb39d20e78819092ea9e04357be008 |
completed | March 31, 2026, 3:04 a.m. |
Created at: March 30, 2026, 5:36 p.m.