Triple
T31335184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life of Henry Wadsworth Longfellow |
E799152
|
entity |
| Predicate | subjectDescribedAs |
P97400
|
FINISHED |
| Object | American poet |
—
|
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: American poet | Statement: [Life of Henry Wadsworth Longfellow, subjectDescribedAs, American poet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectDescribedAs Context triple: [Life of Henry Wadsworth Longfellow, subjectDescribedAs, American poet]
-
A.
subjectOfDescription
chosen
Indicates that the subject is the main entity being described or characterized in a given context or statement.
-
B.
subjectPositionDescribed
Indicates that the subject’s spatial or situational position is explicitly described or specified in relation to some reference frame or context.
-
C.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
-
D.
subjectImpliedAs
Indicates that the subject of an action or statement is not explicitly stated but is understood or inferred from context.
-
E.
subjectKey
Indicates that the subject serves as a unique key or identifier used to reference or distinguish an entity in a relationship or dataset.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 29, 2026, 9:16 p.m.