Triple
T29751265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manuel Lobo |
E752905
|
entity |
| Predicate | foundedSettlementType |
P112165
|
FINISHED |
| Object | fortified settlement |
—
|
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: fortified settlement | Statement: [Manuel Lobo, foundedSettlementType, fortified settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedSettlementType Context triple: [Manuel Lobo, foundedSettlementType, fortified settlement]
-
A.
foundedAsSettlementFor
Indicates that one entity was originally established specifically to serve as a settlement for another entity (such as a group, population, or community).
-
B.
colonyTypeFounded
Indicates the specific type or category of colony that was established in a founding event.
-
C.
historicalSettlementType
chosen
Indicates the type or category of settlement an entity was historically classified as (e.g., village, town, city) during a past period.
-
D.
locatedInSettlementFoundedBy
Indicates that something is located in a settlement that was founded by a specified entity.
-
E.
cityFoundedType
Indicates the type or nature of the founding event or origin by which a city was established.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 28, 2026, 7:54 p.m.