Triple
T2501503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montluçon |
E52473
|
entity |
| Predicate | hasOldQuarter |
P14076
|
FINISHED |
| Object | medieval center on a hill above the Cher |
—
|
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 center on a hill above the Cher | Statement: [Montluçon, hasOldQuarter, medieval center on a hill above the Cher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOldQuarter Context triple: [Montluçon, hasOldQuarter, medieval center on a hill above the Cher]
-
A.
hasHistoricQuarter
chosen
Indicates that an entity possesses or contains a historically significant district or quarter as part of its area or structure.
-
B.
isOldest
Indicates that one entity has a greater age than all other relevant entities in the comparison set.
-
C.
hasLegacy
Indicates that an entity leaves behind a lasting impact, influence, or inheritance that continues to exist or be recognized over time.
-
D.
hasMonth
Indicates that something is associated with, occurs in, or is assigned to a specific month.
-
E.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1c9f80c8190b40ada396e184e75 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.