Triple
T37065891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Routes of Santiago de Compostela in France |
E917441
|
entity |
| Predicate | includesTypeOfMonument |
P25584
|
FINISHED |
| Object | Romanesque church |
—
|
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: Romanesque church | Statement: [Routes of Santiago de Compostela in France, includesTypeOfMonument, Romanesque church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTypeOfMonument Context triple: [Routes of Santiago de Compostela in France, includesTypeOfMonument, Romanesque church]
-
A.
monumentType
chosen
Indicates the specific kind or category of monument that an entity is classified as.
-
B.
appliesToMonument
Indicates that something (such as a rule, status, or attribute) is relevant or applicable specifically to a monument.
-
C.
isMonumentClassic
Indicates that a monument exemplifies classic or traditional architectural or historical style.
-
D.
hasMonumentFunction
Indicates that something serves the role or purpose of a monument, such as commemorating, honoring, or symbolizing a person, event, or idea.
-
E.
isMonumentNumber
Indicates that one entity is the official monument identification number assigned to another entity.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.