Triple
T14683514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cotton Market |
E344846
|
entity |
| Predicate | oftenLocatedNear |
P115314
|
FINISHED |
| Object | transport hubs |
—
|
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: transport hubs | Statement: [Cotton Market, oftenLocatedNear, transport hubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenLocatedNear Context triple: [Cotton Market, oftenLocatedNear, transport hubs]
-
A.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
B.
locatedNearPass
Indicates that one entity is situated close to a mountain pass or similar passageway.
-
C.
situatedNextTo
Indicates that one entity is located immediately beside another, with no significant separation between them.
-
D.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
E.
locatedInOrAdjacentTo
Indicates that one entity is either situated within the boundaries of another entity or directly next to it, sharing a common border or edge.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56a51ec8190941684fd562a7182 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:28 a.m.