Triple
T15672193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bow and arrows of Apollo |
E377340
|
entity |
| Predicate | representsAspectOfApollo |
P64550
|
FINISHED |
| Object | destructive power |
—
|
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: destructive power | Statement: [bow and arrows of Apollo, representsAspectOfApollo, destructive power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsAspectOfApollo Context triple: [bow and arrows of Apollo, representsAspectOfApollo, destructive power]
-
A.
portraysApolloAs
Indicates that one entity represents or depicts Apollo in a particular way or role.
-
B.
symbolicAspect
chosen
Indicates that one entity functions as a symbol or emblem that represents, expresses, or conveys a particular meaning, quality, or concept of another entity.
-
C.
roleInApollo
Indicates that an entity holds or held a specific role or position within the Apollo program or an Apollo mission.
-
D.
onAspect
Indicates that one entity is positioned on a particular side, surface, or facet of another entity.
-
E.
governsAspectOf
Indicates that one entity exercises control, regulation, or determining influence over a particular aspect or component 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f13b1b08190beabc9f4098aa096 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.