Triple
T8301662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkish Wikinews |
E194361
|
entity |
| Predicate | allowsAnonymousEditing |
P273
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Turkish Wikinews, allowsAnonymousEditing, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsAnonymousEditing Context triple: [Turkish Wikinews, allowsAnonymousEditing, yes]
-
A.
isFreeToEdit
Indicates that an entity has permission or the ability to modify or update another entity without restriction.
-
B.
supportsConcurrentEditing
Indicates that multiple users can edit the same item or resource at the same time without blocking one another.
-
C.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
D.
isEditableIn
Indicates that an entity can be modified or changed within a specified context, environment, or container.
-
E.
allowsText
Indicates that one entity permits or supports the use, input, or display of textual content in relation to 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e891030819097f4a26992a8b469 |
completed | March 31, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.