Triple
T11547480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oribos |
E273807
|
entity |
| Predicate | gameRoleForPlayers |
P100060
|
FINISHED |
| Object | main player hub in Shadowlands |
—
|
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: main player hub in Shadowlands | Statement: [Oribos, gameRoleForPlayers, main player hub in Shadowlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameRoleForPlayers Context triple: [Oribos, gameRoleForPlayers, main player hub in Shadowlands]
-
A.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
B.
lineupRole
Indicates the specific role or position an entity holds within a lineup or ordered group.
-
C.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
D.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
E.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e3ad548190b2c88332f5d919bd |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822f00a088190ac6b48e45e743899 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:37 p.m.