Triple
T25737975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue Malher |
E648127
|
entity |
| Predicate | hasNearbyHistoricDistrict |
P72879
|
FINISHED |
| Object | Le Marais |
—
|
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: Le Marais | Statement: [Rue Malher, hasNearbyHistoricDistrict, Le Marais]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHistoricDistrict Context triple: [Rue Malher, hasNearbyHistoricDistrict, Le Marais]
-
A.
hasNearbyHistoricArea
chosen
Indicates that one entity is located close to another entity that is designated as a historic area.
-
B.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
-
C.
hasHistoricCenterNearby
Indicates that one entity is located close to another entity that serves as a historic center or historically significant core area.
-
D.
isHistoricDistrict
Indicates that an area has been officially recognized or designated as a historic district due to its historical, cultural, or architectural significance.
-
E.
hasNearbyCulturalDistrict
Indicates that an entity is located close to a designated cultural district or area with concentrated cultural activities.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 22, 2026, 3:36 a.m.