Triple
T35753641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TELCO |
E1033381
|
entity |
| Predicate | widelyRecognizedAs |
P144403
|
FINISHED |
| Object | abbreviation of Tata Motors |
—
|
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: abbreviation of Tata Motors | Statement: [TELCO, widelyRecognizedAs, abbreviation of Tata Motors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widelyRecognizedAs Context triple: [TELCO, widelyRecognizedAs, abbreviation of Tata Motors]
-
A.
isWidelyKnownAs
chosen
Indicates that an entity is commonly referred to or recognized by a particular name or label by a broad audience.
-
B.
reconocidaPor
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
C.
oftenRecognizedBy
Indicates that one entity is frequently identified, acknowledged, or noticed by another entity.
-
D.
celebratedAs
Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
-
E.
organFamousFor
Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
- 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_69f7a199ab248190acb81776a46011bf |
completed | May 3, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.