Triple
T18937410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cycnus |
E463283
|
entity |
| Predicate | intendsToDecorate |
P88492
|
FINISHED |
| Object | temple of Ares with human heads |
—
|
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: temple of Ares with human heads | Statement: [Cycnus, intendsToDecorate, temple of Ares with human heads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendsToDecorate Context triple: [Cycnus, intendsToDecorate, temple of Ares with human heads]
-
A.
hasDecor
Indicates that one entity possesses, features, or is adorned with a particular decorative element or style.
-
B.
relatedDecoration
Indicates that one decoration is associated with, complements, or is contextually linked to another decoration.
-
C.
decoratedFor
Indicates that an entity has received a decoration, award, or honor in recognition of a specific action, service, or achievement.
-
D.
intendsTo
chosen
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
-
E.
containsDecorationFrom
Indicates that one entity includes or incorporates a decorative element that originates from 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3e8fdb48190ae70cb23c5bc2c97 |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.