Triple
T20437230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brobenah |
E501280
|
entity |
| Predicate | isInInlandArea |
P140131
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Brobenah, isInInlandArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInInlandArea Context triple: [Brobenah, isInInlandArea, true]
-
A.
isInlandTown
Indicates that a town is located away from the coast, without direct access to the sea or ocean.
-
B.
isInlandFrom
Indicates that one place lies away from the coast, further toward the interior of the land, relative to another place.
-
C.
isInlandCity
Indicates that a city is located away from the coast, without direct access to the sea or ocean.
-
D.
hasInlandArea
Indicates that an entity possesses a portion of its territory or surface that is located away from coastal or shoreline areas.
-
E.
isInlandSettlement
Indicates that a settlement is located away from the coast, without direct access to the sea or ocean.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f042988190948253a3d2ee4e9e |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:31 a.m.