Triple
T17349305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constance |
E421763
|
entity |
| Predicate | hasOldTownCharacteristics |
P105746
|
FINISHED |
| Object | medieval street layout |
—
|
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: medieval street layout | Statement: [Constance, hasOldTownCharacteristics, medieval street layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOldTownCharacteristics Context triple: [Constance, hasOldTownCharacteristics, medieval street layout]
-
A.
oldTownCharacter
chosen
Indicates that something possesses the distinctive qualities or atmosphere typically associated with an old town.
-
B.
hasDowntownCharacteristic
Indicates that something possesses a feature, quality, or attribute typically associated with a downtown area.
-
C.
isInOldTownArea
Indicates that an entity is located within the designated old town area of a place.
-
D.
hasSmallTownCharacter
Indicates that something possesses the qualities or atmosphere typically associated with a small town, such as intimacy, familiarity, and a close-knit community feel.
-
E.
hasTraditionalHouseStyle
Indicates that an entity possesses or is characterized by a traditional style of house or residential architecture.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2af5f88190b4c292ca30993b36 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.