Triple
T25642646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro.com |
E642873
|
entity |
| Predicate | providesToContractors |
P17063
|
FINISHED |
| Object | lead generation |
—
|
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: lead generation | Statement: [Pro.com, providesToContractors, lead generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesToContractors Context triple: [Pro.com, providesToContractors, lead generation]
-
A.
launchContractor
Indicates that one entity serves as the contractor responsible for carrying out or managing the launch of another entity.
-
B.
primaryContractor
Indicates that one entity serves as the main responsible contractor for a project, agreement, or work in relation to another entity.
-
C.
providesThat
Indicates that one entity stipulates, specifies, or sets forth a condition, rule, or provision that applies to another entity or situation.
-
D.
contractingOutVia
Indicates that one party delegates or outsources a task, service, or responsibility to another party through a contractual arrangement.
-
E.
suppliesTo
chosen
Indicates that one entity provides or delivers goods, services, or resources to another entity.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 21, 2026, 5:46 p.m.