Triple
T16677554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rise Up |
E405251
|
entity |
| Predicate | isReworkedFrom |
P93604
|
FINISHED |
| Object | In It to Win It |
—
|
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: In It to Win It | Statement: [Rise Up, isReworkedFrom, In It to Win It]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReworkedFrom Context triple: [Rise Up, isReworkedFrom, In It to Win It]
-
A.
includesReworkedMaterialFrom
chosen
Indicates that one entity incorporates or is derived from modified, revised, or otherwise reworked material originating in another entity.
-
B.
reworkedBy
Indicates that an existing work, product, or result has been modified, revised, or substantially altered by a particular agent.
-
C.
reforgedFrom
Indicates that something has been newly created or remade by reshaping or reworking a previous object or material.
-
D.
hasReconstructionWork
Indicates that an entity is undergoing, has undergone, or is associated with reconstruction or restoration work.
-
E.
repairedIn
Indicates that an item or object underwent repair within a specified location or during a particular time period.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37d6c805c81909fbe4fcb20eedbe1 |
completed | April 18, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.