Triple
T28593508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Wikibooks |
E723715
|
entity |
| Predicate | accountPolicy |
P1051
|
FINISHED |
| Object | single user login |
—
|
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: single user login | Statement: [Tamil Wikibooks, accountPolicy, single user login]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accountPolicy Context triple: [Tamil Wikibooks, accountPolicy, single user login]
-
A.
protectionPolicy
Indicates that one entity establishes or enforces rules or measures to safeguard another entity from harm, loss, or risk.
-
B.
publicPolicy
Indicates that an entity is a government or institutional rule, principle, or course of action intended to address public issues or guide societal outcomes.
-
C.
admissionPolicy
Indicates the rules or criteria governing whether and how entities are allowed to be admitted or granted access.
-
D.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
E.
governingPolicy
chosen
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:21 a.m.