Triple
T13119610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starman |
E311687
|
entity |
| Predicate | grantsEffect |
P100810
|
FINISHED |
| Object | temporary invincibility |
—
|
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: temporary invincibility | Statement: [Starman, grantsEffect, temporary invincibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsEffect Context triple: [Starman, grantsEffect, temporary invincibility]
-
A.
grantsStatusEffect
chosen
Indicates that one entity applies or bestows a specific status effect onto another entity.
-
B.
believedToGrant
Indicates that something is thought or assumed to provide, confer, or bestow a particular benefit, quality, or effect.
-
C.
affectsBenefit
Indicates that one entity has an influence on, modifies, or determines the benefit or advantage received by another entity.
-
D.
grantsCreditFor
Indicates that one entity recognizes or awards academic or other formal credit to another entity for a specific activity, course, or achievement.
-
E.
claimsEffect
Indicates that one entity asserts or states that another entity has a particular effect or impact.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98196e69081909111407ee3d9f08e |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.