Triple
T23358305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JMB Diamond |
E593111
|
entity |
| Predicate | priorityAccess |
P152008
|
FINISHED |
| Object | airport services |
—
|
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: airport services | Statement: [JMB Diamond, priorityAccess, airport services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priorityAccess Context triple: [JMB Diamond, priorityAccess, airport services]
-
A.
priorityApplication
Indicates that one application is given precedence or higher processing priority over others.
-
B.
priorityBenefit
Indicates that one benefit takes precedence over or is considered more important than another in a given context.
-
C.
priorityRule
Indicates that one entity is given precedence or higher processing order over another according to a defined rule or policy.
-
D.
priorityGroup
Indicates that one entity is assigned to, or associated with, a particular level or category of priority relative to others.
-
E.
limitsPriorityOf
Indicates that one entity imposes a maximum allowable priority level on another entity’s priority.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a196b308190bfe9bb4b6e7ec363 |
completed | April 29, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:29 p.m.