Triple
T24386527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sixmilebridge |
E614763
|
entity |
| Predicate | hasSettlementFeature |
P64802
|
FINISHED |
| Object | main street |
—
|
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: main street | Statement: [Sixmilebridge, hasSettlementFeature, main street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettlementFeature Context triple: [Sixmilebridge, hasSettlementFeature, main street]
-
A.
hasSettlementCharacteristic
chosen
Indicates that a settlement possesses a specific attribute, feature, or quality.
-
B.
isSettlement
Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
-
C.
hasSubsettlement
Indicates that one settlement includes another, smaller settlement as a subordinate or component part.
-
D.
isKeySettlementOn
Indicates that a settlement serves as a primary or strategically important location situated on a specified route, feature, or area.
-
E.
hasPortSettlement
Indicates that a place has a settlement located at or directly associated with a port for maritime or water-based transport.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29454c36c8190b7820dbf5af7b695 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.