Triple
T12251442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maison de Jeanne d'Arc |
E291979
|
entity |
| Predicate | visitorInformationAvailableIn |
P54718
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [Maison de Jeanne d'Arc, visitorInformationAvailableIn, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorInformationAvailableIn Context triple: [Maison de Jeanne d'Arc, visitorInformationAvailableIn, French]
-
A.
visitorInformation
chosen
Indicates that information or details are provided for or about visitors in relation to a particular place, service, or event.
-
B.
visitorCenter
Indicates that a location serves as a visitor center for a place, providing information or services to visitors of that place.
-
C.
visitorAttractionStatus
Indicates the current operational or accessibility status of a visitor attraction (e.g., open, closed, restricted).
-
D.
visitorAccessPoint
Indicates a location or interface through which visitors are allowed to enter, connect, or gain access to a place, system, or resource.
-
E.
visitorCentreOpened
Indicates that a visitor centre has begun operating or has been officially opened to the public.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.