Triple
T6636976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC United of Manchester |
E150480
|
entity |
| Predicate | supporterOwnershipPercentage |
P7881
|
FINISHED |
| Object | majority fan-owned |
—
|
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: majority fan-owned | Statement: [FC United of Manchester, supporterOwnershipPercentage, majority fan-owned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supporterOwnershipPercentage Context triple: [FC United of Manchester, supporterOwnershipPercentage, majority fan-owned]
-
A.
supportersTrustOwnership
Indicates that supporters have ownership stakes or controlling interests in the entity they support.
-
B.
supportPercentage
Indicates the proportion or share of total backing, approval, or assistance that one entity provides to or receives from another, typically expressed as a percentage.
-
C.
typicalNumberOfHolders
Indicates the usual or expected number of entities that hold or possess a given item, role, or resource.
-
D.
ownershipStructure
chosen
Indicates how ownership or control is distributed among entities within an organization or asset.
-
E.
sharesHeldBy
Indicates that a specified number or portion of shares is owned or held by a particular entity.
- 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_69c687f0ceb08190bf40807bfc605fa5 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:59 p.m.