Triple
T19832269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | king of Tiryns |
E476491
|
entity |
| Predicate | causeOfAuthority |
P99388
|
FINISHED |
| Object | favor of Hera |
—
|
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: favor of Hera | Statement: [king of Tiryns, causeOfAuthority, favor of Hera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfAuthority Context triple: [king of Tiryns, causeOfAuthority, favor of Hera]
-
A.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
-
B.
authorityBasedOn
chosen
Indicates that one entity’s authority or power is derived from, justified by, or contingent upon another specified basis or source.
-
C.
claimedAuthorityFrom
Indicates that one entity asserts its authority, legitimacy, or right to act is derived from another specified source or entity.
-
D.
stanceOnAuthority
Indicates an entity’s attitude, position, or level of support or opposition toward authority or authoritative control.
-
E.
authority
Indicates that one entity has the power, right, or official capacity to direct, control, or make decisions for another entity or over a particular domain.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656cf7e488190b4be28b5e7b363bf |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.