Triple
T38273254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ONCAP |
E1021273
|
entity |
| Predicate | usesCapitalFrom |
P197438
|
FINISHED |
| Object | Onex-sponsored funds |
—
|
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: Onex-sponsored funds | Statement: [ONCAP, usesCapitalFrom, Onex-sponsored funds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCapitalFrom Context triple: [ONCAP, usesCapitalFrom, Onex-sponsored funds]
-
A.
usesCapitalization
Indicates that one entity applies specific capitalization (such as upper/lower case or title case) to another entity, typically a string or text element.
-
B.
startUseAsCapital
Indicates that an entity begins to function or be designated as the capital of a specified political or administrative unit.
-
C.
possibleCapital
Indicates that a location is a candidate or potential capital city of a given political or administrative entity.
-
D.
setInCapital
Indicates that something is located or takes place within the capital city of a given region or country.
-
E.
capitalizedOn
Indicates that one entity took advantage of, exploited, or made beneficial use of an opportunity, situation, or resource provided or created by another entity.
- F. None of above. chosen
Provenance (4 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
| PDg | Predicate description generation | batch_69fe9137730c81909d1d57c30566c89a |
completed | May 9, 2026, 1:43 a.m. |
Created at: May 3, 2026, 4:30 p.m.