Triple
T30144273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BR-040 |
E766209
|
entity |
| Predicate | hasConcessionSections |
P17433
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [BR-040, hasConcessionSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConcessionSections Context triple: [BR-040, hasConcessionSections, yes]
-
A.
hasConcessions
chosen
Indicates that one entity provides or contains concession facilities, services, or rights (such as food, drink, or merchandise sales) for another entity or within a given context.
-
B.
concessionIncludes
Indicates that one concession contains, comprises, or encompasses another concession as a part or subset.
-
C.
concessionArea
Indicates that one entity is a designated concession area associated with or located within another entity (such as a venue, facility, or site).
-
D.
hasConcessionaire
Indicates that one entity is designated as the concessionaire (holder of operating or usage rights under a concession) for another entity.
-
E.
concessionType
Indicates the specific kind or category of concession (such as a discount, exemption, or special allowance) that applies in a given context.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00d820a7788190a8d54625cd87be68 |
completed | May 10, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_6a00d7c5b40c8190b80413238d04e81e |
completed | May 10, 2026, 7:08 p.m. |
Created at: April 29, 2026, 7:18 p.m.