Triple
T8152183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Écuries d’Augias |
E190357
|
entity |
| Predicate | belongsToAuthorCorpus |
P67055
|
FINISHED |
| Object | works of Sully Prudhomme |
—
|
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: works of Sully Prudhomme | Statement: [Les Écuries d’Augias, belongsToAuthorCorpus, works of Sully Prudhomme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToAuthorCorpus Context triple: [Les Écuries d’Augias, belongsToAuthorCorpus, works of Sully Prudhomme]
-
A.
hasPartOfCorpus
chosen
Indicates that one entity constitutes a component or segment of the overall corpus associated with another entity.
-
B.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
C.
hasAuthorRelationshipToSubject
Indicates that an entity serves as the author or creator of the specified subject.
-
D.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
E.
authorBelongsTo
Indicates that an author is affiliated with, or is a member of, a particular organization, group, or 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4483799c81908e73f9a87ed99185 |
completed | March 31, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.