Triple
T32094142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTT Communications Shining Arcs |
E819680
|
entity |
| Predicate | hasCorporateTeamStatus |
—
|
GENERATED |
| Object | true |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorporateTeamStatus Context triple: [NTT Communications Shining Arcs, hasCorporateTeamStatus, true]
-
A.
hasCorporateTeamOrigin
Indicates that an entity originates from, was formed by, or is otherwise derived from a specific corporate team.
-
B.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
C.
hasCurrentTeam
Indicates that an entity is presently a member of or affiliated with a specific team.
-
D.
officialStatusWithTeam
Indicates that an entity holds or has held an official role, position, or status in relation to a specific team.
-
E.
corporateTeamOf
Indicates that one entity is a member of, or belongs to, the same corporate team or organizational unit as another entity.
- F. None of above. chosen
Provenance (1 batch)
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. |
Created at: May 1, 2026, 12:25 a.m.