Triple
T14480825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erastes |
E359096
|
entity |
| Predicate | obligationTowardEromenos |
P81322
|
FINISHED |
| Object | material support |
—
|
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: material support | Statement: [Erastes, obligationTowardEromenos, material support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obligationTowardEromenos Context triple: [Erastes, obligationTowardEromenos, material support]
-
A.
obligation
Indicates that one entity is bound or required to perform a duty, action, or fulfill a condition toward another entity or according to a rule or agreement.
-
B.
hasSocialObligationsTo
chosen
Indicates that one entity bears social duties, expectations, or responsibilities toward another entity.
-
C.
έχειΕραστή
Indicates that someone has or is involved with a lover or romantic partner outside a primary relationship.
-
D.
attitudeTowardLove
Indicates an entity’s feelings, beliefs, or stance regarding the concept or experience of love.
-
E.
encouragesRomanceBetween
Indicates that one entity promotes, supports, or fosters a romantic relationship between two other entities.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924a576c819098351efabdb779b1 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.