Triple
T3931711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akali Phula Singh |
E90807
|
entity |
| Predicate | moralReputation |
P47751
|
FINISHED |
| Object | strict disciplinarian |
—
|
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: strict disciplinarian | Statement: [Akali Phula Singh, moralReputation, strict disciplinarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moralReputation Context triple: [Akali Phula Singh, moralReputation, strict disciplinarian]
-
A.
moralStatus
Indicates the ethical standing or degree of moral consideration that one entity has in relation to another.
-
B.
hasMoralCharacteristic
chosen
Indicates that an entity possesses a particular moral quality, trait, or ethical attribute.
-
C.
moralAssociation
Indicates a perceived ethical or moral connection between entities, such as one influencing or reflecting the moral character, values, or judgment of the other.
-
D.
hasMoralCode
Indicates that an entity adheres to or is guided by a set of moral principles or ethical rules.
-
E.
mottoReputation
Indicates that a particular motto is associated with and characterizes the reputation or public image of an 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeda98058819094dd6ab223670860 |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.