Triple
T38243518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont Samson |
E1013831
|
entity |
| Predicate | toponyme |
P98809
|
FINISHED |
| Object | Pont Samson |
—
|
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: Pont Samson | Statement: [Pont Samson, toponyme, Pont Samson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toponyme Context triple: [Pont Samson, toponyme, Pont Samson]
-
A.
toponymsShareSpelling
Indicates that two place names share the same or very similar written form or spelling.
-
B.
legacyToponym
Indicates that one place name is an older or former name historically used to refer to the same geographic entity as another place name.
-
C.
toponymicFunction
chosen
Indicates that one entity functions as a place-related name or designation for another entity, typically identifying or characterizing it by a geographic location.
-
D.
toponymReflects
Indicates that a place name embodies, mirrors, or expresses some characteristic, feature, or aspect of the place it denotes.
-
E.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of 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.