Triple
T14666373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Barlow |
E344385
|
entity |
| Predicate | sharesHeld |
P26829
|
FINISHED |
| Object | major stakeholder in Sydney FC |
—
|
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: major stakeholder in Sydney FC | Statement: [Scott Barlow, sharesHeld, major stakeholder in Sydney FC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesHeld Context triple: [Scott Barlow, sharesHeld, major stakeholder in Sydney FC]
-
A.
sharesHeldBy
Indicates that a specified number or portion of shares is owned or held by a particular entity.
-
B.
sharesOutstanding
Indicates the total number of a company’s shares that are currently issued and held by all shareholders, excluding any shares the company has repurchased.
-
C.
privateShareOfStock
Indicates that one entity privately transfers or allocates shares of stock to another entity, outside of a public market transaction.
-
D.
representsSharesOf
chosen
Indicates that one entity holds or owns shares or equity interests in another entity.
-
E.
sharesSymbol
Indicates that two entities use or are associated with the same identifying symbol (such as a ticker, code, or notation).
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54c69f8819080a37161deecfba8 |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.