Triple
T4198541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godrej family |
E86009
|
entity |
| Predicate | hasWealthRanking |
P25601
|
FINISHED |
| Object | among richest families in India |
—
|
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: among richest families in India | Statement: [Godrej family, hasWealthRanking, among richest families in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWealthRanking Context triple: [Godrej family, hasWealthRanking, among richest families in India]
-
A.
adjustedWealthRanking
Indicates a comparative ordering of entities based on their wealth after applying specified adjustments or normalization factors.
-
B.
hasWealthType
Indicates that an entity possesses or is associated with a particular category or type of wealth.
-
C.
wealthRanking
chosen
Indicates the relative ordering of entities based on their level of wealth or financial resources.
-
D.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
E.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af036243b4819097efe6b796823cd9 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:48 p.m.