Triple
T38243521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont Samson |
E1013831
|
entity |
| Predicate | géréPar |
P86
|
FINISHED |
| Object | collectivité locale de Bayeux |
—
|
NE NERFINISHED |
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: collectivité locale de Bayeux | Statement: [Pont Samson, géréPar, collectivité locale de Bayeux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: géréPar Context triple: [Pont Samson, géréPar, collectivité locale de Bayeux]
-
A.
administeredBy
chosen
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
-
B.
wirdGeleitetVon
Indicates that something (such as an organization, project, or process) is being led or directed by a specific person or entity.
-
C.
managerFrom
Indicates that one entity serves as a manager originating from, or associated with, a specified source such as an organization, location, or department.
-
D.
managingFor
Indicates that one entity is responsible for directing, supervising, or overseeing activities, resources, or operations on behalf of another entity.
-
E.
laterManagedBy
Indicates that an entity was, at a subsequent time, managed or overseen by another entity.
- 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.