Triple
T26942750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nova Corps |
E678562
|
entity |
| Predicate | abilityGranted |
P67649
|
FINISHED |
| Object | superhuman strength |
—
|
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: superhuman strength | Statement: [Nova Corps, abilityGranted, superhuman strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abilityGranted Context triple: [Nova Corps, abilityGranted, superhuman strength]
-
A.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
-
B.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
C.
grantsAbility
chosen
Indicates that one entity endows another entity with a specific capability or power that it did not previously possess.
-
D.
placeGranted
Indicates that one entity has been given or allocated a position, spot, or placement by another entity.
-
E.
grantedStatus
Indicates that an entity has been officially approved or given a particular status, permission, or privilege.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620822d6081908e38814f5a1c0931 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:19 a.m.