Triple
T10837014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heaven Hart |
E255784
|
entity |
| Predicate | basedOnSourcesUpTo |
P95981
|
FINISHED |
| Object | 2024 |
—
|
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: 2024 | Statement: [Heaven Hart, basedOnSourcesUpTo, 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnSourcesUpTo Context triple: [Heaven Hart, basedOnSourcesUpTo, 2024]
-
A.
requiresSources
Indicates that something must be supported, justified, or validated by one or more external sources.
-
B.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
-
C.
basedOnResource
Indicates that one entity is derived from, created using, or conceptually dependent on another entity as its underlying resource.
-
D.
laterSources
Indicates that the information, claim, or reference is derived from sources that were created or recorded at a later time than the event or material being discussed.
-
E.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d746ff70148190b844ab92d796af6c |
completed | April 9, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:19 p.m.