Triple
T37520726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life of William Congreve |
E932764
|
entity |
| Predicate | biographicalForm |
P92894
|
FINISHED |
| Object | prose |
—
|
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: prose | Statement: [Life of William Congreve, biographicalForm, prose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biographicalForm Context triple: [Life of William Congreve, biographicalForm, prose]
-
A.
biographicalStatus
Indicates the current life status or condition of a person in a biographical context (e.g., living, deceased, unknown).
-
B.
hasBiographicalStyle
chosen
Indicates that something is characterized by or presented in a biographical manner or style.
-
C.
usesBiographicalStructure
Indicates that one entity employs or is organized according to the biographical structure of another entity (e.g., a work structured around a person’s life story).
-
D.
hasBiographicalNote
Indicates that an entity is associated with a textual note summarizing or describing a person’s life or background.
-
E.
hasBiographicalWork
Indicates that there exists a biographical work (such as a book, article, or film) whose subject is the given 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.