Triple
T28181879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labyrinthe Géant de Guéret |
E716052
|
entity |
| Predicate | hasVisitorCategory |
P1284
|
FINISHED |
| Object | families |
—
|
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: families | Statement: [Labyrinthe Géant de Guéret, hasVisitorCategory, families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorCategory Context triple: [Labyrinthe Géant de Guéret, hasVisitorCategory, families]
-
A.
hasVisitorType
chosen
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
B.
hasVisitorCharacteristic
Indicates that a visitor possesses or exhibits a particular characteristic, attribute, or quality.
-
C.
hasCheckInCategory
Indicates that an entity is associated with a specific category or type of check-in event.
-
D.
hasTicketCategory
Indicates that an item, event, or access right is associated with a specific ticket category or type.
-
E.
hasTypeOfVisitorExperience
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 10:20 p.m.