Triple
T18102966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Φιλική Εταιρεία |
E433275
|
entity |
| Predicate | σχεδιάζει |
P66258
|
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.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
B.
plan
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
C.
planning
chosen
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
D.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
E.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with 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_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. |
Created at: April 10, 2026, 10:28 a.m.