Triple
T29211884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budhan |
E740566
|
entity |
| Predicate | associatedWithCommunication |
—
|
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: associatedWithCommunication Context triple: [Budhan, associatedWithCommunication, true]
-
A.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
B.
associatedWithGeneral
chosen
Indicates a non-specific or broad relationship or connection exists between entities without detailing its precise nature.
-
C.
associatedWithRelationship
Indicates a general connection or involvement between entities through some form of relationship, without specifying its exact nature.
-
D.
associatedWithUse
Indicates a relationship where one entity is connected to or involved in the use or utilization of another entity.
-
E.
associatedWithComplex
Indicates that an entity has a relationship or connection with a specific complex, such as being part of it, interacting with it, or functionally linked to it.
- F. None of above.
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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 12:11 p.m.