Triple
T35252301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waray Wikisource |
E1018125
|
entity |
| Predicate | hasProjectPolicy |
P35521
|
FINISHED |
| Object | free content |
—
|
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: free content | Statement: [Waray Wikisource, hasProjectPolicy, free content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProjectPolicy Context triple: [Waray Wikisource, hasProjectPolicy, free content]
-
A.
hasPolicyStatus
Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
-
B.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
-
C.
hasUserAccessPolicy
Indicates that a specific access control policy is defined or associated for a user’s permissions or usage of a resource.
-
D.
hasReferencePolicy
chosen
Indicates that an entity is governed by or associated with a specific reference policy that defines how it should be used, accessed, or managed.
-
E.
hasEnrollmentPolicy
Indicates that there is a specific rule or set of rules governing who may enroll in, access, or participate in something and under what conditions.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.