Triple
T1491036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Standard Tribe |
E29578
|
entity |
| Predicate | pointOfView |
P1924
|
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: [Eastern Standard Tribe, pointOfView, first-person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointOfView Context triple: [Eastern Standard Tribe, pointOfView, first-person]
-
A.
perspectiveOf
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
-
B.
viewpointFrom
Indicates a relationship where something is observed, depicted, or described from the perspective or location of a particular entity or point.
-
C.
narrativePerspective
chosen
Indicates the point of view or vantage from which a narrative is told, specifying the relationship between the storyteller and the events being described.
-
D.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
-
E.
viewOnReality
Indicates a subject’s overarching perspective, interpretation, or conceptual stance regarding the nature of reality.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c3ace4819081bc2b86ee2486b6 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.