Triple
T7168132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anschutz Corporation |
E167122
|
entity |
| Predicate | hasInterestIn |
P66206
|
FINISHED |
| Object | sports teams |
—
|
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: sports teams | Statement: [Anschutz Corporation, hasInterestIn, sports teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterestIn Context triple: [Anschutz Corporation, hasInterestIn, sports teams]
-
A.
subjectInterest
chosen
Indicates that the subject has an interest in, or is concerned with, the object.
-
B.
publicInterestStatus
Indicates that something has been evaluated or designated in terms of its relevance, importance, or impact to the general public or society at large.
-
C.
hasAreaOfInterest
Indicates that an entity possesses or is associated with a particular area of interest or focus.
-
D.
hasPetInterest
Indicates that one entity has an interest in, affinity for, or concern about pets in relation to another entity or context.
-
E.
recognizedInterest
Indicates that one entity has formally acknowledged or identified another entity’s interest in something as valid or relevant.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e85b4410819098c6531229da51d4 |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:48 p.m.