Triple
T11781183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landhi Industrial Area |
E280148
|
entity |
| Predicate | distanceToPortQasim_km |
P101549
|
FINISHED |
| Object | approximately 10–15 |
—
|
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: approximately 10–15 | Statement: [Landhi Industrial Area, distanceToPortQasim_km, approximately 10–15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToPortQasim_km Context triple: [Landhi Industrial Area, distanceToPortQasim_km, approximately 10–15]
-
A.
distanceFromKarachi
Indicates the measured spatial distance between a given entity’s location and the city of Karachi.
-
B.
distanceToLahore_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Lahore.
-
C.
distanceToNasiriyah
Indicates the spatial distance between a given entity and the location of Nasiriyah.
-
D.
distanceFromJeddah
Indicates the measured spatial distance between a given entity and the location of Jeddah.
-
E.
distanceToAlKhums_km
Indicates the physical distance, measured in kilometers, between an entity and the location of Al Khums.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
| PDg | Predicate description generation | batch_69d8a8c07d648190b8650d31f3a15090 |
completed | April 10, 2026, 7:37 a.m. |
Created at: April 8, 2026, 9:42 p.m.