Triple
T4223136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Class |
E94388
|
entity |
| Predicate | groundService |
P55407
|
FINISHED |
| Object | lounge access |
—
|
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: lounge access | Statement: [Upper Class, groundService, lounge access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundService Context triple: [Upper Class, groundService, lounge access]
-
A.
groundComponent
Indicates that one entity serves as a foundational or base part upon which another entity is built, attached, or functionally dependent.
-
B.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
C.
coversGrounds
Indicates that one entity extends over, occupies, or lies across the surface area of another entity (typically land or grounds).
-
D.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
E.
serviceFor
Indicates that one entity provides a service or performs functions on behalf 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e4bf6088190926b982039a12079 |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e4ace648190acf911853d4fcf86 |
completed | March 12, 2026, 11:37 p.m. |
Created at: March 12, 2026, 11:04 p.m.