Triple
T11192199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pannawonica |
E264828
|
entity |
| Predicate | isPlannedSettlement |
P36957
|
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: [Pannawonica, isPlannedSettlement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlannedSettlement Context triple: [Pannawonica, isPlannedSettlement, true]
-
A.
isSettlement
Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
-
B.
isRemoteSettlement
Indicates that a settlement is located in a remote, sparsely connected, or isolated area relative to major population centers or infrastructure.
-
C.
isPlannedCity
chosen
Indicates that a city has been deliberately designed and constructed according to a pre-established urban plan rather than developing organically over time.
-
D.
isSettlementOf
Indicates that one entity is a settlement (such as a town, village, or city) that belongs to, is located within, or is administratively part of another entity.
-
E.
isLocatedInSettlement
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8be025481909d311b587418dfb2 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.