Triple
T16827449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Acquico |
E409057
|
entity |
| Predicate | assetTypeAcquired |
P7185
|
FINISHED |
| Object | professional sports league |
—
|
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: professional sports league | Statement: [Alpha Acquico, assetTypeAcquired, professional sports league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assetTypeAcquired Context triple: [Alpha Acquico, assetTypeAcquired, professional sports league]
-
A.
assetType
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
B.
acquisitionType
chosen
Indicates the specific kind or category of acquisition relationship that exists between entities (such as a company buying another company, assets, or a controlling stake).
-
C.
asset
Indicates that one entity is a valuable resource, item, or property owned, controlled, or beneficially used by another entity.
-
D.
acquiredFor
Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third entity.
-
E.
ownsAssetType
Indicates that an entity possesses ownership rights over an asset of a specified type.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b31404c88190a3b2802842ca77eb |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.