Triple
T30163607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stele of the Vultures |
E766733
|
entity |
| Predicate | sideDescription |
P168508
|
FINISHED |
| Object | historical side with battle scenes |
—
|
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: historical side with battle scenes | Statement: [Stele of the Vultures, sideDescription, historical side with battle scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideDescription Context triple: [Stele of the Vultures, sideDescription, historical side with battle scenes]
-
A.
sideBContent
Indicates the content or material that appears on the B side of a two-sided item or medium.
-
B.
side2
Indicates that an entity is positioned on, associated with, or corresponds to the second side of another entity or structure.
-
C.
sideAContent
Indicates that the content or information pertains specifically to side A of a two-sided entity or relationship.
-
D.
side
Indicates that one entity is located at, aligned with, or associated with the lateral part or edge of another entity.
-
E.
locationSide
Indicates that one entity is positioned on a particular side (e.g., left, right, front, back) relative to another entity or reference point.
- F. None of above. chosen
Provenance (4 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f054d248190b5f5fabda89e172b |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:22 p.m.