Triple
T24529442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brightline premium lounge |
E606760
|
entity |
| Predicate | accessWith |
P51771
|
FINISHED |
| Object | Brightline premium fare |
—
|
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: Brightline premium fare | Statement: [Brightline premium lounge, accessWith, Brightline premium fare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessWith Context triple: [Brightline premium lounge, accessWith, Brightline premium fare]
-
A.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
B.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
C.
accessDeterminedBy
Indicates that the ability to access a resource is governed or controlled by a specified condition, rule, or authority.
-
D.
accessStatus
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
E.
accessProvides
chosen
Indicates that one entity grants or enables the ability to use, enter, or retrieve another entity or resource.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.