Triple
T13592006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewar Airport |
E324712
|
entity |
| Predicate | connectivityPlannedWith |
P82020
|
FINISHED |
| Object | road network |
—
|
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: road network | Statement: [Jewar Airport, connectivityPlannedWith, road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectivityPlannedWith Context triple: [Jewar Airport, connectivityPlannedWith, road network]
-
A.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
-
B.
platformPlanned
Indicates that a platform is intended or scheduled to be created, implemented, or made available in the future.
-
C.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
D.
connectivityFeatures
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
-
E.
plannedVia
chosen
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb056ce088190a6feb4266633d18b |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.