Triple
T35753575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYSE:TTM |
E1033379
|
entity |
| Predicate | hasUnderlyingFoundedByGroup |
P8758
|
FINISHED |
| Object | Tata Group |
—
|
NE NERFINISHED |
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: Tata Group | Statement: [NYSE:TTM, hasUnderlyingFoundedByGroup, Tata Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderlyingFoundedByGroup Context triple: [NYSE:TTM, hasUnderlyingFoundedByGroup, Tata Group]
-
A.
underlyingFoundedBy
chosen
Indicates that an entity’s foundational creation or establishment is ultimately attributable to another entity, which serves as its underlying founder.
-
B.
isGroupUnder
Indicates that one group is organizationally or hierarchically subordinate to, or contained within, another group.
-
C.
hasUnderlyingEntity
Indicates that one entity serves as the fundamental or base entity upon which another entity is conceptually or structurally built.
-
D.
revealedAsSubgroupOf
Indicates that one group has been newly identified or exposed as being a subgroup or subset of another group.
-
E.
foundedAsGrouping
Indicates that an entity was originally established or created as part of a particular group, category, or organizational grouping.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:06 p.m.