Triple
T30025647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tata Sons |
E762873
|
entity |
| Predicate | roleInTataGroup |
P199503
|
FINISHED |
| Object | principal holding company |
—
|
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: principal holding company | Statement: [Tata Sons, roleInTataGroup, principal holding company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTataGroup Context triple: [Tata Sons, roleInTataGroup, principal holding company]
-
A.
roleInToyotaGroup
Indicates that an entity holds a specific role or position within the organizational structure of the Toyota Group.
-
B.
roleInToyota
Indicates that one entity holds a specific role, position, or function within the organization Toyota.
-
C.
roleWithinDaimler
Indicates that one entity holds or has held a specific role, position, or function within the Daimler organization.
-
D.
roleInTesla
Indicates that one entity holds or held a specific role, position, or function within the organization Tesla.
-
E.
roleAtMercedes
Indicates that an entity holds or held a specific role or position at Mercedes.
- F. None of above. chosen
Provenance (4 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
| PDg | Predicate description generation | batch_69ff3fb151008190bf8a90f9f1c5f0c8 |
completed | May 9, 2026, 2:07 p.m. |
Created at: April 29, 2026, 6:48 p.m.