Triple
T15455639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariaeus |
E371761
|
entity |
| Predicate | laterDealtWith |
P118879
|
FINISHED |
| Object | Greek mercenaries of the Ten Thousand |
—
|
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: Greek mercenaries of the Ten Thousand | Statement: [Ariaeus, laterDealtWith, Greek mercenaries of the Ten Thousand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDealtWith Context triple: [Ariaeus, laterDealtWith, Greek mercenaries of the Ten Thousand]
-
A.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
B.
laterWrittenDownIn
Indicates that information, events, or content were recorded or documented at a later time than when they originally occurred or were created.
-
C.
laterProvidedFor
Indicates that one entity is supplied, arranged, or made available for another entity at a subsequent time rather than initially.
-
D.
heldAfter
Indicates that one event or state occurs or is maintained at some point in time after another specified event or state.
-
E.
laterFlag
Indicates that one event, state, or action occurs at a time later than another referenced event, state, or action.
- F. None of above. chosen
Provenance (4 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f146a2c8190882741af3ec15268 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:31 a.m.