Triple
T3880045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corporate Executive Board |
E92797
|
entity |
| Predicate | servedClientFunction |
P47301
|
FINISHED |
| Object | finance |
—
|
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: finance | Statement: [Corporate Executive Board, servedClientFunction, finance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedClientFunction Context triple: [Corporate Executive Board, servedClientFunction, finance]
-
A.
performedFunction
chosen
Indicates that an entity has carried out or executed a particular function, role, or operation.
-
B.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
C.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
D.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an entity.
-
E.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.