Triple
T35392774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arwal |
E1022984
|
entity |
| Predicate | hasNearbyRegionalHub |
P84435
|
FINISHED |
| Object | Jehanabad |
—
|
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: Jehanabad | Statement: [Arwal, hasNearbyRegionalHub, Jehanabad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyRegionalHub Context triple: [Arwal, hasNearbyRegionalHub, Jehanabad]
-
A.
hasRegionalCenterNearby
chosen
Indicates that a regional center is located in close proximity to the referenced entity.
-
B.
hasNeighborhoodHub
Indicates that one place serves as a central local hub or focal point for community activities within a particular neighborhood.
-
C.
isRegionalHubOn
Indicates that an entity functions as a primary regional hub or central node located on or served by a specified network, route, or infrastructure.
-
D.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
E.
hasNearbyHeadquarters
Indicates that the headquarters of two entities are located geographically close to each other.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
Created at: May 3, 2026, 4:03 p.m.