Triple
T38243520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont Samson |
E1013831
|
entity |
| Predicate | accessibilité |
P88924
|
FINISHED |
| Object | accès public |
—
|
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: accès public | Statement: [Pont Samson, accessibilité, accès public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessibilité Context triple: [Pont Samson, accessibilité, accès public]
-
A.
accessible
Indicates that one entity can be reached, entered, used, or understood by another entity, often without undue difficulty or barriers.
-
B.
cultAccessibility
Indicates how easily a cult can be approached, joined, or engaged with by individuals or groups.
-
C.
accessibilityFeatures
Indicates the specific tools, settings, or design elements provided to make something usable or understandable for people with disabilities or diverse access needs.
-
D.
accessibleAs
Indicates that one entity can be reached, used, or obtained through another entity, often as an alternative form, route, or representation.
-
E.
visitorAccessibility
chosen
Indicates how easily or suitably a place, service, or resource can be used or reached by visitors, including those with varying needs or abilities.
- 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.