Triple
T28643999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian Wikisource |
E725003
|
entity |
| Predicate | openToEditsBy |
P164894
|
FINISHED |
| Object | registered users |
—
|
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: registered users | Statement: [Persian Wikisource, openToEditsBy, registered users]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openToEditsBy Context triple: [Persian Wikisource, openToEditsBy, registered users]
-
A.
openToEditsFrom
chosen
Indicates that one entity permits another entity to modify or revise its content or configuration.
-
B.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
C.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
D.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
E.
opensBy
Indicates that one entity is opened, unlocked, or made accessible through the use or action 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 4:47 a.m.