Triple
T6313603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepsi Max |
E141561
|
entity |
| Predicate | isPackagedIn |
P49317
|
FINISHED |
| Object | aluminum can |
—
|
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: aluminum can | Statement: [Pepsi Max, isPackagedIn, aluminum can]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPackagedIn Context triple: [Pepsi Max, isPackagedIn, aluminum can]
-
A.
includesPackage
chosen
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
B.
isDeployedFrom
Indicates that one entity originates, is launched, or put into operation from another specified source or location.
-
C.
hasPackageName
Indicates that an entity (such as a software component or module) is associated with a specific package name identifier.
-
D.
alsoDefinedInPackage
Indicates that the same element or concept is additionally defined or declared in another software package.
-
E.
integratedIn
Indicates that one entity is incorporated as a component or part within a larger system, structure, or context represented by another entity.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064a075dc8190acf7ec010cb4b00c |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:28 p.m.