Triple
T27809239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Château de la Belle au Bois Dormant |
E702473
|
entity |
| Predicate | parkRole |
P163374
|
FINISHED |
| Object | visual centerpiece |
—
|
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: visual centerpiece | Statement: [Le Château de la Belle au Bois Dormant, parkRole, visual centerpiece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkRole Context triple: [Le Château de la Belle au Bois Dormant, parkRole, visual centerpiece]
-
A.
parkRole
chosen
Indicates the functional role or designated purpose an entity has within a park or park-related context.
-
B.
parkAuthority
Indicates that an entity has official responsibility for managing, regulating, or overseeing a park or protected recreational area.
-
C.
parkSection
Indicates a relationship where a specific area or subsection belongs to, is contained within, or is designated as part of a larger park.
-
D.
parkType
Indicates the specific category or classification of a park based on its designated use, management, or characteristics.
-
E.
parkSystem
Indicates a relationship where an entity is part of, managed by, or associated with an organized system of parks or protected recreational areas.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:41 p.m.