Triple
T28627799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Wikipedia |
E724567
|
entity |
| Predicate | hasAdminUsers |
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: [Italian Wikipedia, hasAdminUsers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdminUsers Context triple: [Italian Wikipedia, hasAdminUsers, true]
-
A.
hasAdministratorUsers
chosen
Indicates that an entity is associated with one or more users who have administrative privileges or responsibilities over it.
-
B.
hasAdminInterface
Indicates that an entity provides or is associated with an administrative interface for configuration, management, or control tasks.
-
C.
hasAdministrativeType
Indicates that an entity is associated with a specific category or level of administrative classification (such as type of jurisdiction or administrative unit).
-
D.
hasUsers
Indicates that an entity is associated with one or more users who use, own, or are linked to it.
-
E.
hasAdministrationMethod
Indicates the method or route by which something (typically a drug, treatment, or resource) is administered or delivered.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 4:36 a.m.