Triple
T23284765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musée d’Archéologie de Nice-Cimiez |
E588955
|
entity |
| Predicate | hasOutdoorComponent |
P150260
|
FINISHED |
| Object | archaeological site |
—
|
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: archaeological site | Statement: [Musée d’Archéologie de Nice-Cimiez, hasOutdoorComponent, archaeological site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorComponent Context triple: [Musée d’Archéologie de Nice-Cimiez, hasOutdoorComponent, archaeological site]
-
A.
hasOutdoorType
Indicates that an entity is associated with a specific type or category of outdoor environment or feature.
-
B.
hasOutdoorSection
chosen
Indicates that something includes or is associated with a designated area located outdoors.
-
C.
hasOutdoorFocus
Indicates a relationship where an entity is primarily concerned with, oriented toward, or specialized in outdoor environments, activities, or contexts.
-
D.
isOutdoor
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
-
E.
hasOutdoorResource
Indicates that an entity is associated with, provides, or includes access to an outdoor resource or facility.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1964600888190b40ecbefdc8aec64 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:59 p.m.