Triple
T38363031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monitor Group |
E892346
|
entity |
| Predicate | servedClientTypes |
P82339
|
FINISHED |
| Object | corporations |
—
|
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: corporations | Statement: [Monitor Group, servedClientTypes, corporations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedClientTypes Context triple: [Monitor Group, servedClientTypes, corporations]
-
A.
operatedForClientType
Indicates that an operation or service is performed specifically on behalf of, or tailored to, a particular type or category of client.
-
B.
intendedClients
chosen
Indicates the entities that a product, service, or action is specifically designed or targeted to serve as clients.
-
C.
hasNotableClientType
Indicates that an entity has clients belonging to a particular notable or distinguished category or type.
-
D.
clientProvides
Indicates that a client supplies, delivers, or makes available a product, service, or resource to another party.
-
E.
servesDestinationType
Indicates that an entity provides service to, or is intended for use with, a specific type or category of destination.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00a2f0d1588190a936ea7df0ef0464 |
completed | May 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_6a00a28ccd94819085b5e123f5a4769e |
completed | May 10, 2026, 3:21 p.m. |
Created at: May 3, 2026, 4:31 p.m.