Triple
T13211238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedroom Kandi |
E314496
|
entity |
| Predicate | hasConsultants |
P108519
|
FINISHED |
| Object | independent sales consultants |
—
|
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: independent sales consultants | Statement: [Bedroom Kandi, hasConsultants, independent sales consultants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConsultants Context triple: [Bedroom Kandi, hasConsultants, independent sales consultants]
-
A.
hasCounsel
Indicates that one entity serves as a legal advisor or representative (counsel) for another entity.
-
B.
consultsOn
Indicates that one entity provides expert advice, guidance, or professional input to another entity regarding a specific subject, project, or decision.
-
C.
hasConsultativeBody
Indicates that an entity is associated with a consultative body that provides advice, recommendations, or guidance on its decisions or activities.
-
D.
hasStakeholder
Indicates that an entity is a stakeholder of another entity, typically having an interest, involvement, or influence in its activities or outcomes.
-
E.
consulted
Indicates that one entity sought advice, information, or guidance from 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9e072c8190b66e2c2430628ed0 |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:17 p.m.