Triple
T18034572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AKEL |
E431472
|
entity |
| Predicate | hasCoreSupportBase |
P60372
|
FINISHED |
| Object | Greek Cypriot community |
—
|
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 Cypriot community | Statement: [AKEL, hasCoreSupportBase, Greek Cypriot community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreSupportBase Context triple: [AKEL, hasCoreSupportBase, Greek Cypriot community]
-
A.
hasSupportBase
Indicates that one entity serves as the supporting base or foundation upon which another entity rests, is mounted, or is structurally stabilized.
-
B.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
C.
hasSupportBaseIn
chosen
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
D.
hasCoreService
Indicates that an entity provides, includes, or is associated with a primary or fundamental service that forms the central part of its offering or functionality.
-
E.
hasCoreFunction
Indicates that one entity serves as a primary or essential function or role of 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be38766c8190ae95701f4575469c |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.