Triple
T18102951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Φιλική Εταιρεία |
E433275
|
entity |
| Predicate | στρατολογεί |
P130442
|
FINISHED |
| Object | Έλληνες εμπόρους |
—
|
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: Έλληνες εμπόρους | Statement: [Φιλική Εταιρεία, στρατολογεί, Έλληνες εμπόρους]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: στρατολογεί Context triple: [Φιλική Εταιρεία, στρατολογεί, Έλληνες εμπόρους]
-
A.
commanderOfGreekForces
Indicates that one entity serves as the commanding leader of the Greek military forces in a given context or conflict.
-
B.
الاستراتيجية
Indicates a strategic relationship in which an entity plans, organizes, or directs actions and resources to achieve specific long-term goals or advantages.
-
C.
AthenianCommander
Indicates that the subject serves as a military commander for the Athenians or the Athenian state.
-
D.
strategicCommand
Indicates that one entity issues high-level, overarching directives or plans that guide the actions or decisions of another entity.
-
E.
fleetStrategy
Indicates the overarching plan or approach governing how a group of vehicles or vessels is organized, deployed, and operated to achieve specific objectives.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb7be948190b4ed4586f731d6f2 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:28 a.m.