Triple
T27371621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 12/30 |
E690337
|
entity |
| Predicate | cityOrDistrict |
P163488
|
FINISHED |
| Object | Ambala |
—
|
NE NERFINISHED |
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: Ambala | Statement: [Runway 12/30, cityOrDistrict, Ambala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOrDistrict Context triple: [Runway 12/30, cityOrDistrict, Ambala]
-
A.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
B.
inCityDistrict
Indicates that one entity is located within the boundaries of a specific city district.
-
C.
cityOrTown
Indicates that the subject is classified as a city or a town.
-
D.
targetCityDistrict
Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
-
E.
citySubdivision
Indicates that one administrative or geographic unit is a smaller subdivision contained within a larger city.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638344b148190bf0414ef7c5f1f38 |
completed | May 2, 2026, 5:45 p.m. |
Created at: April 27, 2026, 12:19 p.m.