Triple
T30316008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfred Powerpack |
E771056
|
entity |
| Predicate | isAddOnFor |
P142693
|
FINISHED |
| Object | Alfred |
—
|
NE NERFINISHED |
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: Alfred | Statement: [Alfred Powerpack, isAddOnFor, Alfred]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAddOnFor Context triple: [Alfred Powerpack, isAddOnFor, Alfred]
-
A.
canBeAddedTo
chosen
Indicates that one entity is capable of being combined or incorporated with another entity, typically without conflict or incompatibility.
-
B.
isOfferedBy
Indicates that a service, product, or opportunity is provided or made available by a particular entity.
-
C.
isAdditiveFor
Indicates that one entity can be combined with another in a way that their effects or quantities sum together to produce a cumulative result.
-
D.
isAppanageFor
Indicates that something is granted or assigned as an appanage (a hereditary or dependent possession) for a particular person or group.
-
E.
alsoSupports
Indicates that an entity, in addition to its primary or previously stated function, provides support for another entity, feature, or activity.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68193b2b08190a00f08dbba490563 |
completed | May 2, 2026, 10:58 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:51 p.m.