Triple
T6809200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alec Waugh |
E156586
|
entity |
| Predicate | hasGenreInBibliography |
P73127
|
FINISHED |
| Object | autobiography |
—
|
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: autobiography | Statement: [Alec Waugh, hasGenreInBibliography, autobiography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenreInBibliography Context triple: [Alec Waugh, hasGenreInBibliography, autobiography]
-
A.
hasBibliographicCategory
Indicates that an entity is associated with a specific bibliographic classification or category within a cataloging or documentation system.
-
B.
hasBibliography
Indicates that one entity includes or is associated with a bibliography listing referenced or related works.
-
C.
hasGenreOfClaim
Indicates that a claim is categorized or classified under a particular genre or type of claim.
-
D.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
-
E.
hasCanonicalGenre
Indicates that an entity is associated with its primary or officially recognized genre classification.
- F. None of above. chosen
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_69c68828b26c819090fe9df7612bbc27 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30c741881909e220b05aa564bc2 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d2a8f9188190abbb8c730e7b5edf |
completed | March 27, 2026, 6:55 p.m. |
Created at: March 27, 2026, 2:16 p.m.