Triple
T33644381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romang |
E861917
|
entity |
| Predicate | hasPrimarySettlementsLocation |
P203620
|
FINISHED |
| Object | coastal areas |
—
|
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: coastal areas | Statement: [Romang, hasPrimarySettlementsLocation, coastal areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySettlementsLocation Context triple: [Romang, hasPrimarySettlementsLocation, coastal areas]
-
A.
hasMajorSettlementsType
Indicates that an entity is associated with major settlements of a specified type (e.g., cities, towns, villages).
-
B.
hasSecondaryCity
Indicates that an entity possesses or is associated with a secondary city in addition to its primary city.
-
C.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
D.
hasPrimarySettlementFunction
Indicates that a settlement’s main or dominant functional role (e.g., residential, commercial, industrial, administrative) is of the specified type.
-
E.
hasMajorSettlementRegion
Indicates that a major settlement is located within or primarily associated with a particular geographic region.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01b3af7b908190b4675c85d32d106c |
completed | May 11, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_6a01b35813c081908e484b2b9ca5dd05 |
completed | May 11, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_6a01b3ae7f948190b93fbe0add0dbcec |
completed | May 11, 2026, 10:47 a.m. |
Created at: May 1, 2026, 1:42 a.m.