Triple
T26857937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carcès |
E676245
|
entity |
| Predicate | hasMedievalVillageCenter |
P179466
|
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: [Carcès, hasMedievalVillageCenter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedievalVillageCenter Context triple: [Carcès, hasMedievalVillageCenter, true]
-
A.
hasMedievalCityCenter
Indicates that a place possesses a historically preserved or identifiable city center originating from the medieval period.
-
B.
hasMedievalBuilding
Indicates that one entity possesses, contains, or includes a building dating from the medieval period.
-
C.
isVillageCenterOf
Indicates that a location functions as the central or main hub area of a specified village.
-
D.
hasCentralTownFeature
Indicates that a town possesses a specific central feature or focal element (such as a landmark, square, or facility) that characterizes its core area.
-
E.
hasMedievalStreetPattern
Indicates that an area’s street layout follows or preserves a characteristic medieval pattern of routes, blocks, and spaces.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 27, 2026, 5:22 a.m.