Triple
T198180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Emblem of India |
E4042
|
entity |
| Predicate | restrictedUse |
P1050
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [State Emblem of India, restrictedUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restrictedUse Context triple: [State Emblem of India, restrictedUse, yes]
-
A.
restriction
chosen
Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
-
B.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
C.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
D.
reservedFor
Indicates that something is set aside or allocated specifically for the use, benefit, or purpose of a particular entity or group.
-
E.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25be47ea881909c296b30a0d47a65 |
completed | Feb. 28, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69a25b47481c8190add47c641c977bb9 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.