Triple
T24882698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porte Saint-Lazare |
E622754
|
entity |
| Predicate | isInHistoricEnsemble |
P157436
|
FINISHED |
| Object | Historic Centre of Avignon |
—
|
NE NERFINISHED |
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: Historic Centre of Avignon | Statement: [Porte Saint-Lazare, isInHistoricEnsemble, Historic Centre of Avignon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInHistoricEnsemble Context triple: [Porte Saint-Lazare, isInHistoricEnsemble, Historic Centre of Avignon]
-
A.
isInHistoricRegister
Indicates that an entity has been officially listed or recorded in a recognized historic register or registry.
-
B.
isInHistoricRegion
Indicates that an entity is located within or belongs to a historically recognized geographic region.
-
C.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
D.
isHistoricRegionFor
Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
-
E.
isHistoricSee
Indicates that one entity serves or functioned as a historically significant viewing point or place from which another entity is or was seen.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f4303fad6c8190844f069164f0904d |
completed | May 1, 2026, 4:46 a.m. |
Created at: April 18, 2026, 5:24 a.m.