Triple
T32094143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTT Communications Shining Arcs |
E819680
|
entity |
| Predicate | industryOfOwner |
P45634
|
FINISHED |
| Object | telecommunications |
—
|
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: telecommunications | Statement: [NTT Communications Shining Arcs, industryOfOwner, telecommunications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industryOfOwner Context triple: [NTT Communications Shining Arcs, industryOfOwner, telecommunications]
-
A.
ownerSector
chosen
Indicates the sector or industry category to which the owner of an entity belongs.
-
B.
occupantIndustry
Indicates the industry or sector in which an occupant (such as a tenant or user of a space) operates.
-
C.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
D.
industrySectorOfBuilder
Indicates the industry sector in which a given builder (such as a company or organization that constructs or develops something) operates.
-
E.
industryOfUnderlyingCompany
Indicates the industry sector in which the underlying company associated with this entity operates.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:25 a.m.