Triple
T24548850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phyleus |
E607301
|
entity |
| Predicate | tookSideWith |
P17585
|
FINISHED |
| Object | Heracles |
—
|
NE NERFINISHED |
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: Heracles | Statement: [Phyleus, tookSideWith, Heracles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookSideWith Context triple: [Phyleus, tookSideWith, Heracles]
-
A.
unionSide
Indicates that an entity is aligned with, represents, or acts on behalf of a labor union in a labor-related relationship or context.
-
B.
defectedTo
Indicates that an entity abandoned its original side, group, or allegiance and joined or gave support to another, typically opposing, side.
-
C.
side
Indicates that one entity is located at, aligned with, or associated with the lateral part or edge of another entity.
-
D.
supportedSide
chosen
Indicates that one entity backed, favored, or provided assistance to a particular side or party in a conflict, dispute, or competition.
-
E.
onSide
Indicates that one entity is positioned along or adjacent to the side 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8cb6dc081909bf37123d82ed2c9 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.