Triple
T29278588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue Vivienne |
E742307
|
entity |
| Predicate | hasCoveredPassage |
P202134
|
FINISHED |
| Object | Galerie Vivienne |
—
|
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: Galerie Vivienne | Statement: [Rue Vivienne, hasCoveredPassage, Galerie Vivienne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoveredPassage Context triple: [Rue Vivienne, hasCoveredPassage, Galerie Vivienne]
-
A.
hasBeenCoveredBy
Indicates that something has received coverage or treatment by another entity, such as being reported on, discussed, or addressed.
-
B.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
-
C.
hasCoveredEvent
Indicates that one entity has reported on, documented, or provided coverage of a particular event.
-
D.
hasCoveredStands
Indicates that a venue or facility includes spectator stands that are sheltered by a roof or other overhead covering.
-
E.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a0058c341ac8190825067dc25158839 |
completed | May 10, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_6a005857249c81908b27587b84d84dbb |
completed | May 10, 2026, 10:05 a.m. |
| PDg | Predicate description generation | batch_6a0058c26638819085d8cbaa0bd4ccf0 |
completed | May 10, 2026, 10:06 a.m. |
Created at: April 28, 2026, 12:52 p.m.