Triple
T8041634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iberians |
E187453
|
entity |
| Predicate | hadSettlementFeature |
P80704
|
FINISHED |
| Object | defensive walls |
—
|
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: defensive walls | Statement: [Iberians, hadSettlementFeature, defensive walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSettlementFeature Context triple: [Iberians, hadSettlementFeature, defensive walls]
-
A.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
B.
hadPrimarySettlementPattern
Indicates that an entity exhibited or was characterized by a particular dominant form or arrangement of human settlement.
-
C.
hasFormerSettlement
Indicates that a location previously contained a settlement that no longer exists or is no longer inhabited.
-
D.
hasHumanSettlementAlong
Indicates that a human settlement is located adjacent to or distributed along the length of a specified geographic feature or route.
-
E.
hasCityStatusSettlement
Indicates that a settlement possesses official recognition or designation as a city.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f1e98508190a29a7bb5055f8ba0 |
completed | March 31, 2026, 3:27 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:23 p.m.