Triple
T29010387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A.S.C.H.–S.C.H.A. (Lettres dansantes) |
E736546
|
entity |
| Predicate | workTitleIncludesLetters |
P112144
|
FINISHED |
| Object | A.S.C.H. |
—
|
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: A.S.C.H. | Statement: [A.S.C.H.–S.C.H.A. (Lettres dansantes), workTitleIncludesLetters, A.S.C.H.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workTitleIncludesLetters Context triple: [A.S.C.H.–S.C.H.A. (Lettres dansantes), workTitleIncludesLetters, A.S.C.H.]
-
A.
workTitleContains
chosen
Indicates that the title of a work includes a specified substring or term.
-
B.
workTitleType
Indicates the specific category or type of a work’s title (e.g., main title, alternative title, translated title) in relation to that work.
-
C.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
D.
hasTitleLetter
Indicates that an entity possesses a specific letter or character within its title.
-
E.
workTitle
Indicates the formal title or name of a work (such as a book, artwork, or composition) associated with an 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fdb92508190bd0e7fe7877cdae2 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:41 a.m.