Triple
T28631204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Wikipedia |
E724642
|
entity |
| Predicate | hasArbitrationCommittee |
P1396
|
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: [Ukrainian Wikipedia, hasArbitrationCommittee, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArbitrationCommittee Context triple: [Ukrainian Wikipedia, hasArbitrationCommittee, true]
-
A.
hasTechnicalCommittee
Indicates that an entity is associated with or overseen by a specific technical committee.
-
B.
hasCommittee
chosen
Indicates that an entity is associated with or overseen by a specific committee.
-
C.
independentCommittee
Indicates that a committee operates autonomously, without control or undue influence from other entities or stakeholders.
-
D.
hasArbitrator
Indicates that an entity is assigned or associated with an arbitrator who is responsible for resolving its disputes or conflicts.
-
E.
hasCommitteeMembers
Indicates that a committee is composed of, or includes, specific individuals as its members.
- 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_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 4:37 a.m.