Triple
T29341624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MDK2 |
E744050
|
entity |
| Predicate | hasPerspectiveOption |
P50557
|
FINISHED |
| Object | third-person view |
—
|
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 view | Statement: [MDK2, hasPerspectiveOption, third-person view]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerspectiveOption Context triple: [MDK2, hasPerspectiveOption, third-person view]
-
A.
hasPerspectiveEffect
Indicates that one entity visually appears altered in size, shape, or position relative to another due to perspective or viewpoint.
-
B.
settingOfPerspective
Indicates the contextual situation, environment, or circumstances within which a particular perspective or point of view is framed or expressed.
-
C.
providesOption
chosen
Indicates that one entity makes a particular choice, alternative, or configuration available to another entity.
-
D.
hasParticularView
Indicates that one entity holds, expresses, or is characterized by a specific opinion, perspective, or standpoint regarding something.
-
E.
hasPerspectiveGalleryLength
Indicates the length measurement associated with a perspective gallery in a given context or structure.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 28, 2026, 1:34 p.m.