Triple
T4019233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concourse E |
E91238
|
entity |
| Predicate | regulatesAccess |
P15393
|
FINISHED |
| Object | ticketed passengers only |
—
|
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: ticketed passengers only | Statement: [Concourse E, regulatesAccess, ticketed passengers only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesAccess Context triple: [Concourse E, regulatesAccess, ticketed passengers only]
-
A.
controlsAccessTo
chosen
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
B.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
C.
regulatesWith
Indicates that one entity controls, modulates, or influences the activity, state, or behavior of another entity through some regulatory mechanism or interaction.
-
D.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
E.
regulatesIn
Indicates that one entity controls, modulates, or influences the activity, expression, or behavior of another entity within a system or process.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaab39d4819080e37cd175c89542 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.