Triple
T5880865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marketing and Regulatory Programs Business Services |
E130744
|
entity |
| Predicate | clientAgencyType |
P49812
|
FINISHED |
| Object | marketing agencies |
—
|
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: marketing agencies | Statement: [Marketing and Regulatory Programs Business Services, clientAgencyType, marketing agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientAgencyType Context triple: [Marketing and Regulatory Programs Business Services, clientAgencyType, marketing agencies]
-
A.
partnerAgency
Indicates a formal collaborative relationship in which one agency acts as a partner to another agency.
-
B.
componentAgency
Indicates that one entity functions as a constituent or subordinate agency within the organizational structure of another agency.
-
C.
developingAgency
Indicates that one entity serves as the organization or agency responsible for developing or creating another entity.
-
D.
agencyTypeOfOperator
chosen
Indicates the specific type or category of agency to which the operator belongs or by which the operator is characterized.
-
E.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.