Triple
T29010385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A.S.C.H.–S.C.H.A. (Lettres dansantes) |
E736546
|
entity |
| Predicate | associatedTownSpelling |
P203888
|
FINISHED |
| Object | A–S–C–H |
E1846291
|
NE 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: A–S–C–H | Statement: [A.S.C.H.–S.C.H.A. (Lettres dansantes), associatedTownSpelling, A–S–C–H]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTownSpelling Context triple: [A.S.C.H.–S.C.H.A. (Lettres dansantes), associatedTownSpelling, A–S–C–H]
-
A.
sharesSpellingWith
Indicates that two entities have identical or substantially identical written forms (i.e., they are spelled the same way).
-
B.
toponymsShareSpelling
Indicates that two place names share the same or very similar written form or spelling.
-
C.
associatedCityNameTransliteration
Indicates that an entity is linked to a city whose name is given in a transliterated (phonetic or romanized) form.
-
D.
spellingReplacedBy
Indicates that one spelling of a term has been superseded or substituted by another spelling.
-
E.
usedAsTownNameFor
Indicates that something serves as the official or common name of a particular town.
- F. None of above. chosen
Provenance (5 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a023f290e3081909a465d6cfb79518a |
completed | May 11, 2026, 8:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25379d34008190aa3b2fa6ef409355 |
completed | June 7, 2026, 9:19 a.m. |
| PD | Predicate disambiguation | batch_6a0238d1436c8190ab0251030b01902e |
completed | May 11, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_6a023f27f1608190bac5be9c4c67f527 |
completed | May 11, 2026, 8:42 p.m. |
Created at: April 28, 2026, 9:41 a.m.