Triple
T15513793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distributed Proofreaders |
E368778
|
entity |
| Predicate | hasUserRegistration |
P1077
|
FINISHED |
| Object | required for proofreading |
—
|
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: required for proofreading | Statement: [Distributed Proofreaders, hasUserRegistration, required for proofreading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUserRegistration Context triple: [Distributed Proofreaders, hasUserRegistration, required for proofreading]
-
A.
hasUser
Indicates that an entity is associated with or linked to a specific user.
-
B.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
C.
hasUserService
chosen
Indicates that an entity is associated with or utilizes a particular user-related service.
-
D.
hasRegistrar
Indicates that an entity is formally recorded or overseen by a specific registrar organization or authority.
-
E.
hasRegisterSystem
Indicates that an entity uses or is associated with a particular register system (e.g., a system for recording, tracking, or registering items, events, or participants).
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04031e62c8190953b61207142af15 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:02 a.m.