Triple
T4140997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mani Peninsula |
E89269
|
entity |
| Predicate | hasTraditionalBuildingType |
P50464
|
FINISHED |
| Object | pyrgos (tower house) |
—
|
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: pyrgos (tower house) | Statement: [Mani Peninsula, hasTraditionalBuildingType, pyrgos (tower house)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalBuildingType Context triple: [Mani Peninsula, hasTraditionalBuildingType, pyrgos (tower house)]
-
A.
traditionallyBuiltOver
Indicates that one entity has been constructed on top of another in a manner consistent with long-established or customary building practices.
-
B.
containsBuildingType
chosen
Indicates that a location or area includes at least one building of the specified type.
-
C.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
D.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
-
E.
hasBuildingHeightType
Indicates the classification or type used to characterize the height of a building in the relationship.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.