Triple
T27626541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Investment Bank |
E696222
|
entity |
| Predicate | advisoryArea |
P111844
|
FINISHED |
| Object | strategic corporate 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: strategic corporate finance | Statement: [Investment Bank, advisoryArea, strategic corporate finance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advisoryArea Context triple: [Investment Bank, advisoryArea, strategic corporate finance]
-
A.
assessmentAreaDefinedBy
Indicates that the scope or domain of an assessment is specified or delimited by a particular area or boundary.
-
B.
strategicArea
Indicates that an entity is designated as an area of strategic importance or priority within a broader plan, operation, or context.
-
C.
thematicArea
Indicates the subject or item is associated with, or falls under, a particular thematic area or topic of focus.
-
D.
area of activity
chosen
Indicates the domain, field, or sphere in which an entity is active or carries out its primary functions or operations.
-
E.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
- 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:18 p.m.