Triple
T36549563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bright Lord |
E901221
|
entity |
| Predicate | playablePerspective |
P180779
|
FINISHED |
| Object | third-person |
—
|
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: third-person | Statement: [The Bright Lord, playablePerspective, third-person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playablePerspective Context triple: [The Bright Lord, playablePerspective, third-person]
-
A.
perspectiveOf
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
-
B.
settingOfPerspective
Indicates the contextual situation, environment, or circumstances within which a particular perspective or point of view is framed or expressed.
-
C.
playableSide
Indicates that a particular side, faction, or team in a game can be actively controlled or chosen by the player.
-
D.
playableMode
Indicates that a particular mode, configuration, or state can be actively used or played within a system or application.
-
E.
controlPerspective
chosen
Indicates that one entity determines, influences, or manages the viewpoint or frame of reference through which another entity perceives or represents something.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.