Triple
T20135016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arpitanie |
E491001
|
entity |
| Predicate | hasToponymicHeritage |
P59103
|
FINISHED |
| Object | Arpitan place names |
—
|
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: Arpitan place names | Statement: [Arpitanie, hasToponymicHeritage, Arpitan place names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasToponymicHeritage Context triple: [Arpitanie, hasToponymicHeritage, Arpitan place names]
-
A.
hasToponymy
chosen
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
B.
hasNotableToponym
Indicates that an entity is associated with a place name that is particularly notable, distinctive, or significant.
-
C.
hasToponymicMotivation
Indicates that something is motivated, derived, or named based on a place name (toponym).
-
D.
includesToponym
Indicates that one entity contains or references a place name (toponym) associated with another entity.
-
E.
hasToponymicDerivatives
Indicates that a name or term serves as the source from which related place-based or toponymic names are derived.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66766e46c81908721fd47066dc9f8 |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:32 p.m.