Triple
T38243509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont Samson |
E1013831
|
entity |
| Predicate | usagePrincipal |
P181878
|
FINISHED |
| Object | circulation routière |
—
|
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: circulation routière | Statement: [Pont Samson, usagePrincipal, circulation routière]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usagePrincipal Context triple: [Pont Samson, usagePrincipal, circulation routière]
-
A.
realmUsage
Indicates how a particular realm, domain, or scope is used or applied in relation to another entity or context.
-
B.
usoPrincipal
chosen
Indicates the primary or main way in which something is used or intended to be used in relation to another entity.
-
C.
accessPrinciple
Indicates that one entity has the right, ability, or method to obtain, use, or interact with another entity or resource under defined conditions.
-
D.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
E.
usageCategory
Indicates the classification of how something is used or the type of usage it falls under.
- 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_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.