Triple
T26134462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basta village |
E659338
|
entity |
| Predicate | modernSettlementRelativeTo |
P128342
|
FINISHED |
| Object | Tell Basta |
—
|
NE NERFINISHED |
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: Tell Basta | Statement: [Basta village, modernSettlementRelativeTo, Tell Basta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSettlementRelativeTo Context triple: [Basta village, modernSettlementRelativeTo, Tell Basta]
-
A.
modernSettlement
chosen
Indicates that the subject is a contemporary or currently existing human settlement located at the object.
-
B.
modernSettlementCoreOf
Indicates that a modern settlement functions as the central or primary core area of another, broader settlement entity.
-
C.
modernSettlementArea
Indicates the geographic area occupied by a settlement in its modern or current form.
-
D.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
E.
relativeChronology
Indicates a temporal ordering relationship that specifies how one event or state is positioned in time relative to another (e.g., earlier, later, or overlapping).
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 26, 2026, 8:16 p.m.