Triple
T34554002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ergotelis F.C. |
E887151
|
entity |
| Predicate | hasAttracted |
P1347
|
FINISHED |
| Object | international players |
—
|
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: international players | Statement: [Ergotelis F.C., hasAttracted, international players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttracted Context triple: [Ergotelis F.C., hasAttracted, international players]
-
A.
attracts
chosen
Indicates that one entity exerts a force or influence that draws another entity toward it.
-
B.
succeededByAttraction
Indicates that one attraction or point of interest is directly followed or replaced by another attraction in a sequence or timeline.
-
C.
hasSimilarAttraction
Indicates that two entities experience or exert a comparable level or type of attraction toward something or each other.
-
D.
hasAttractionBasedOn
Indicates that one entity feels an attraction toward another entity that is specifically grounded in a particular basis, criterion, or set of characteristics.
-
E.
has
Indicates that one entity possesses, owns, contains, or includes another entity as part of its state or composition.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72029a73c8190ac6969098273c1eb |
completed | May 3, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.