Triple
T3727721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annals of Sargon II |
E81788
|
entity |
| Predicate | containsPerspective |
P8789
|
FINISHED |
| Object | Assyrian royal viewpoint |
—
|
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: Assyrian royal viewpoint | Statement: [Annals of Sargon II, containsPerspective, Assyrian royal viewpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPerspective Context triple: [Annals of Sargon II, containsPerspective, Assyrian royal viewpoint]
-
A.
perspectiveOf
chosen
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
-
B.
hasViewpointType
Indicates that something is associated with or characterized by a particular type or category of viewpoint or perspective.
-
C.
refersToAspect
Indicates that one entity specifically references or points to a particular aspect, feature, or component of another entity.
-
D.
hasPanoramicView
Indicates that something offers a wide, unobstructed view over a broad surrounding area.
-
E.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf921bc81908bb347d6b9204670 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.