Triple
T35191678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love of Life |
E1016134
|
entity |
| Predicate | hasNotableEarlyAppearance |
P136890
|
FINISHED |
| Object | Raul Julia |
E322245
|
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: Raul Julia | Statement: [Love of Life, hasNotableEarlyAppearance, Raul Julia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEarlyAppearance Context triple: [Love of Life, hasNotableEarlyAppearance, Raul Julia]
-
A.
hasNotableEarlyCareerAppearanceOf
chosen
Indicates that an entity features or includes a significant appearance by another entity during the latter’s early career.
-
B.
hasNotableYear
Indicates that an entity is associated with a specific year that is particularly significant or noteworthy for it.
-
C.
hasNotableMultipleAppearances
Indicates that an entity appears multiple times in a context or medium in a way considered significant or noteworthy.
-
D.
hasNotableShow
Indicates that an entity is associated with a particular show that is considered notable or significant.
-
E.
hasNotableRecognitionAs
Indicates that an entity has received notable recognition, distinction, or status specifically in the role, capacity, or identity denoted by the related entity.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a036fb4650c81908df9b9ec8ed8594b |
completed | May 12, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384019c80081908c26e626c7f73bbb |
completed | June 21, 2026, 7:48 p.m. |
| PD | Predicate disambiguation | batch_6a036f64dc648190a31cf944d3ea0f7d |
completed | May 12, 2026, 6:20 p.m. |
Created at: May 3, 2026, 4:02 p.m.