Triple
T11721417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telephone Communication Limited |
E278639
|
entity |
| Predicate | currentOfficialNameOfTCL |
P66
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Telephone Communication Limited, currentOfficialNameOfTCL, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentOfficialNameOfTCL Context triple: [Telephone Communication Limited, currentOfficialNameOfTCL, false]
-
A.
currentOfficialNameSince
Indicates the date or time from which an entity has borne its current official name.
-
B.
formerOfficialNameOf
Indicates that one entity was previously the official name of another entity before a renaming or reclassification.
-
C.
officialName
chosen
Indicates the formally recognized name assigned to an entity by an authoritative body or source.
-
D.
officialNameSince
Indicates the date or point in time from which a particular official name has been in effect for an entity.
-
E.
firstOfficialName
Indicates the original or primary official name formally assigned to an entity before any subsequent name changes or alternatives.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c373088190bc2ae77a1696d280 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.