Triple
T25156644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Change We Must |
E626330
|
entity |
| Predicate | featuresReworkedMaterialFrom |
P93604
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Change We Must, featuresReworkedMaterialFrom, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresReworkedMaterialFrom Context triple: [Change We Must, featuresReworkedMaterialFrom, Yes]
-
A.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
B.
featuresMaterialType
Indicates that an entity is characterized by or incorporates a specific type of material.
-
C.
includesReworkedMaterialFrom
chosen
Indicates that one entity incorporates or is derived from modified, revised, or otherwise reworked material originating in another entity.
-
D.
originalMaterialFor
Indicates that one entity serves as the source or basis material from which another entity is derived, adapted, or created.
-
E.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 18, 2026, 6:30 a.m.