Triple
T4757014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerberus |
E105612
|
entity |
| Predicate | subduedByMethod |
P44999
|
FINISHED |
| Object | music of Orpheus |
—
|
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: music of Orpheus | Statement: [Cerberus, subduedByMethod, music of Orpheus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subduedByMethod Context triple: [Cerberus, subduedByMethod, music of Orpheus]
-
A.
secondaryMethod
chosen
Indicates that an entity serves as an additional or backup method used alongside or after a primary method in performing an action or achieving a result.
-
B.
subordinateTo
Indicates that one entity holds a lower rank, status, or authority and is subject to the control, direction, or oversight of another entity.
-
C.
dominatedBy
Indicates that one entity is under the control, influence, or overpowering authority of another entity.
-
D.
minimizedBy
Indicates that one entity serves to reduce, lessen, or make as small as possible the value, effect, or impact of another entity.
-
E.
suppressedDuring
Indicates that one event, action, or state is actively prevented, inhibited, or held back while another specified event, condition, or time period is occurring.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64ec16a0819089836e4388b555f6 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.