Triple
T8915415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Actius |
E212283
|
entity |
| Predicate | hasCultFunction |
P47658
|
FINISHED |
| Object | guardian of Actium |
—
|
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: guardian of Actium | Statement: [Apollo Actius, hasCultFunction, guardian of Actium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCultFunction Context triple: [Apollo Actius, hasCultFunction, guardian of Actium]
-
A.
hasCultFeature
Indicates that an entity possesses a characteristic, attribute, or element associated with cultic or ritual practices.
-
B.
hasCulturalFunction
Indicates that something serves a particular role, purpose, or function within a culture or cultural context.
-
C.
hasSacredFunction
chosen
Indicates that something serves a religious or holy role, purpose, or duty within a sacred context.
-
D.
hasCultFollowing
Indicates that something has attracted a small but highly dedicated and enthusiastic group of supporters or fans.
-
E.
hasCulturalFeature
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc660f6a088190b0af829ea809d8ad |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.