Triple
T20296665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minecraft community |
E505368
|
entity |
| Predicate | hostsServerType |
P66298
|
FINISHED |
| Object | Survival Multiplayer servers |
—
|
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: Survival Multiplayer servers | Statement: [Minecraft community, hostsServerType, Survival Multiplayer servers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsServerType Context triple: [Minecraft community, hostsServerType, Survival Multiplayer servers]
-
A.
hostType
Indicates the category or kind of host associated with or responsible for the related entity or activity.
-
B.
hostStarType
Indicates the classification of the star that serves as the primary host for an object, such as a planet or planetary system.
-
C.
hostsUnitType
Indicates that one entity serves as a location or platform that accommodates or contains a specified type of unit.
-
D.
usesServerType
chosen
Indicates that an entity operates on, is hosted by, or otherwise relies on a specific type or category of server.
-
E.
hostsClassification
Indicates that an entity serves as the host or environment in which a particular classification or categorized item resides or is applied.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67707f770819093742d7509fe9bdd |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:15 a.m.