Triple
T36960686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praetor Suit |
E914298
|
entity |
| Predicate | upgradeSystem |
P187454
|
FINISHED |
| Object | Praetor Suit upgrade points |
—
|
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: Praetor Suit upgrade points | Statement: [Praetor Suit, upgradeSystem, Praetor Suit upgrade points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradeSystem Context triple: [Praetor Suit, upgradeSystem, Praetor Suit upgrade points]
-
A.
upgradeProgram
Indicates that one entity improves, enhances, or replaces another entity’s program with a more advanced or updated version.
-
B.
upgradeType
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
-
C.
upgradeMethod
Indicates the method or process by which something is improved, updated, or elevated to a higher level or version.
-
D.
upgradePath
Indicates the relationship by which one entity can be improved, enhanced, or transitioned into another, typically more advanced, version or state.
-
E.
upgradeStatus
Indicates the current state or progress of an upgrade process applied to an entity.
- F. None of above. chosen
Provenance (4 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 3, 2026, 4:14 p.m.