Triple
T2753707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Josh Harris-led ownership group |
E61049
|
entity |
| Predicate | acquiredAssetType |
P15055
|
FINISHED |
| Object | NFL franchise |
—
|
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: NFL franchise | Statement: [Josh Harris-led ownership group, acquiredAssetType, NFL franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquiredAssetType Context triple: [Josh Harris-led ownership group, acquiredAssetType, NFL franchise]
-
A.
acquisitionType
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).
-
B.
assetType
chosen
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
C.
acquiredFor
Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third entity.
-
D.
ownsAssetType
Indicates that an entity possesses ownership rights over an asset of a specified type.
-
E.
hasAcquisitionType
Indicates the specific kind or category of acquisition relationship that exists between one entity acquiring another.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb6ed9c08190824d1866e198ef80 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.