Triple
T28630278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greek Wikipedia |
E724621
|
entity |
| Predicate | supportsAdministrators |
P180225
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Greek Wikipedia, supportsAdministrators, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAdministrators Context triple: [Greek Wikipedia, supportsAdministrators, true]
-
A.
hasAdministratorUsers
chosen
Indicates that an entity is associated with one or more users who have administrative privileges or responsibilities over it.
-
B.
administersFor
Indicates that one entity provides or applies something (such as a treatment, service, or resource) on behalf of or for the benefit of another entity.
-
C.
supportsUsers
Indicates that one entity provides assistance, functionality, or compatibility for the users associated with another entity.
-
D.
supportsMultiuser
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
-
E.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01ac8b4ac881908aa52079c985ddac |
completed | May 11, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_6a01aa7fa7b48190b4911aa6bcabe7eb |
completed | May 11, 2026, 10:07 a.m. |
Created at: April 28, 2026, 4:37 a.m.