Triple
T19079856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babu (Jagdishpur title) |
E466997
|
entity |
| Predicate | hasSocialRank |
P43278
|
FINISHED |
| Object | aristocratic |
—
|
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: aristocratic | Statement: [Babu (Jagdishpur title), hasSocialRank, aristocratic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialRank Context triple: [Babu (Jagdishpur title), hasSocialRank, aristocratic]
-
A.
hasSocialIdentity
Indicates that an entity possesses or is associated with a particular social identity, such as a role, group membership, or socially recognized status.
-
B.
hasSocialInfluenceThrough
Indicates that one entity exerts social influence on another specifically by means of an intermediary channel, platform, or relationship.
-
C.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
D.
hasSocialPosition
chosen
Indicates that an entity occupies or is assigned a particular social status, role, or rank within a social structure or hierarchy.
-
E.
hasSocialService
Indicates that an entity provides, offers, or is associated with a social service to another entity or community.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e82ec08190873186ff51e89d86 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.