Triple
T29010386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A.S.C.H.–S.C.H.A. (Lettres dansantes) |
E736546
|
entity |
| Predicate | associatedNameSpelling |
P24023
|
FINISHED |
| Object | S–C–H–A |
E1846294
|
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: S–C–H–A | Statement: [A.S.C.H.–S.C.H.A. (Lettres dansantes), associatedNameSpelling, S–C–H–A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedNameSpelling Context triple: [A.S.C.H.–S.C.H.A. (Lettres dansantes), associatedNameSpelling, S–C–H–A]
-
A.
nameSpellingStandardized
Indicates that an entity’s name has been normalized to a consistent, standardized spelling form.
-
B.
associatedName
chosen
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
C.
associatedTownSpelling
Indicates that there is a specific spelling variant or form used for the name of an associated town.
-
D.
nicknameSpellingNote
Indicates that there is a note or clarification about how a nickname is spelled in relation to a given name or entity.
-
E.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
- F. None of above.
Provenance (4 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_6a0245e917748190bf0a65db538aa66f |
completed | May 11, 2026, 9:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a251f65bb1c8190a4dafda87386b2f5 |
completed | June 7, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_6a023f7cf7148190af5c2ea501511145 |
completed | May 11, 2026, 8:43 p.m. |
Created at: April 28, 2026, 9:41 a.m.