Triple
T28594450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esperanto Wikipedia |
E723735
|
entity |
| Predicate | hasPolicies |
P82624
|
FINISHED |
| Object | community-written rules |
—
|
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: community-written rules | Statement: [Esperanto Wikipedia, hasPolicies, community-written rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolicies Context triple: [Esperanto Wikipedia, hasPolicies, community-written rules]
-
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.
hasNotablePolicy
Indicates that an entity possesses a policy that is distinguished, significant, or otherwise noteworthy in its context.
-
D.
hasPolicyPage
chosen
Indicates that an entity maintains or is associated with a dedicated policy page, typically outlining rules, terms, or guidelines.
-
E.
appliesPoliciesOf
Indicates that one entity enforces, follows, or implements the policies that originate from or are defined by 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 28, 2026, 4:21 a.m.