Triple
T11563644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molten Core |
E274200
|
entity |
| Predicate | recommendedPlayers |
P100352
|
FINISHED |
| Object | 40 |
—
|
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: 40 | Statement: [Molten Core, recommendedPlayers, 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedPlayers Context triple: [Molten Core, recommendedPlayers, 40]
-
A.
featuresTopPlayersFrom
Indicates that something includes or showcases the most prominent or best-performing players from a specified source or group.
-
B.
featuresPlayersFrom
Indicates that something (such as a work, event, or production) includes or showcases players originating from a specified source, group, or location.
-
C.
featuresTopPlayers
Indicates that something prominently presents or showcases the most outstanding or highly ranked players.
-
D.
managedPlayers
Indicates that one entity has managerial responsibility or authority over the players represented by the other entity.
-
E.
featuresPlayer
Indicates that something includes or prominently presents a particular player as part of its content or composition.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd2016481909b33848af3d1d6c1 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:37 p.m.