Triple
T32094142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTT Communications Shining Arcs |
E819680
|
entity |
| Predicate | hasCorporateTeamStatus |
P204275
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NTT Communications Shining Arcs, hasCorporateTeamStatus, true]
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 (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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a035ead9ee0819099806d2670dc9c50 |
completed | May 12, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_6a035dc9210c8190a9044c6a53211520 |
completed | May 12, 2026, 5:05 p.m. |
| PDg | Predicate description generation | batch_6a035eacf0808190aa124ecc6c753fdf |
completed | May 12, 2026, 5:09 p.m. |
Created at: May 1, 2026, 12:25 a.m.