Triple
T38652799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sally Boyle |
E939801
|
entity |
| Predicate | hasPerspectiveInGame |
P189061
|
FINISHED |
| Object | first-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: first-person | Statement: [Sally Boyle, hasPerspectiveInGame, first-person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerspectiveInGame Context triple: [Sally Boyle, hasPerspectiveInGame, first-person]
-
A.
inGamePerspective
chosen
Indicates that something is being viewed, described, or experienced from within the context and point of view of the game world itself.
-
B.
hasPerspectiveEffect
Indicates that one entity visually appears altered in size, shape, or position relative to another due to perspective or viewpoint.
-
C.
perspectiveOf
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
-
D.
hasPerspectiveOnCombat
Indicates a relationship where an entity holds a particular viewpoint, attitude, or stance regarding combat or warfare.
-
E.
hasViewingPointFor
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 3, 2026, 4:33 p.m.