Triple
T16253858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swordsman Online |
E394579
|
entity |
| Predicate | progressionSystem |
P98703
|
FINISHED |
| Object | experience-based leveling |
—
|
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: experience-based leveling | Statement: [Swordsman Online, progressionSystem, experience-based leveling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: progressionSystem Context triple: [Swordsman Online, progressionSystem, experience-based leveling]
-
A.
hasProgressionSystem
chosen
Indicates that an entity includes or is associated with a structured system through which progress, advancement, or development can occur over time.
-
B.
playerProgressionFrom
Indicates a progression or advancement of a player from one state, level, or stage to another.
-
C.
lifeProgression
Indicates the sequence or advancement of an entity through different stages or phases of its life or development.
-
D.
careerSystem
Indicates a relationship where an entity is part of, governed by, or operates within a particular career-related system or framework.
-
E.
multiplayerProgression
Indicates that multiple participants advance or develop together over time within a shared activity or system.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24598c9488190a92df7d8b1824724 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.