Triple
T30943035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heartman |
E788312
|
entity |
| Predicate | providesToProtagonist |
P49758
|
FINISHED |
| Object | scientific analysis |
—
|
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: scientific analysis | Statement: [Heartman, providesToProtagonist, scientific analysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesToProtagonist Context triple: [Heartman, providesToProtagonist, scientific analysis]
-
A.
wouldProvide
Indicates that one entity is willing or expected to supply or furnish something to another entity under certain conditions.
-
B.
hasProtagonistAbility
Indicates that a protagonist possesses a specific ability, power, or special skill.
-
C.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
D.
helpsProtagonistWith
chosen
Indicates that one entity assists the protagonist in performing, achieving, or dealing with something specified by the other entity.
-
E.
providesThat
Indicates that one entity stipulates, specifies, or sets forth a condition, rule, or provision that applies to another entity or situation.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 29, 2026, 8:53 p.m.