Triple
T35034177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Old Flame |
E1010863
|
entity |
| Predicate | firstIncludedIn |
P140482
|
FINISHED |
| Object | Life Studies |
E309661
|
NE 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: Life Studies | Statement: [The Old Flame, firstIncludedIn, Life Studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIncludedIn Context triple: [The Old Flame, firstIncludedIn, Life Studies]
-
A.
initiallyIncluded
Indicates that an entity was part of a specified set, group, or configuration at the beginning of a process, period, or state.
-
B.
isFirstToInclude
chosen
Indicates that an entity is the earliest or original one to incorporate or contain another specified entity, feature, or element.
-
C.
formerlyIncluded
Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
-
D.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
E.
laterIncludedOn
Indicates that one entity was added to, incorporated into, or featured on another entity at a subsequent time.
- F. None of above.
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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38ae0b04dc8190a378db1c6183e583 |
completed | June 22, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.