Triple
T38061006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squads |
E950338
|
entity |
| Predicate | progressionLinkedTo |
P178351
|
FINISHED |
| Object | multiplayer rank |
—
|
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: multiplayer rank | Statement: [Squads, progressionLinkedTo, multiplayer rank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: progressionLinkedTo Context triple: [Squads, progressionLinkedTo, multiplayer rank]
-
A.
progressionTiedTo
chosen
Indicates that the advancement, development, or continuation of one entity or process is conditionally linked or dependent on the advancement or state of another.
-
B.
progressionScope
Indicates the scope or extent within which a progression, development, or advancement is defined or measured.
-
C.
progressionModel
Indicates a model that represents how something changes, develops, or advances over time or through a sequence of stages.
-
D.
progressedBy
Indicates that an activity, process, or state advances or moves forward as a result of the actions or influence of a specified agent or factor.
-
E.
progressionPosition
Indicates the specific place or rank that something occupies within an ordered sequence, series, or progression.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:21 p.m.