Triple
T809788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Ten Conference |
E17517
|
entity |
| Predicate | revenueRanking |
P2342
|
FINISHED |
| Object | among highest of NCAA conferences |
—
|
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: among highest of NCAA conferences | Statement: [Big Ten Conference, revenueRanking, among highest of NCAA conferences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revenueRanking Context triple: [Big Ten Conference, revenueRanking, among highest of NCAA conferences]
-
A.
revenue
Indicates the amount of income generated by an entity from its business activities or operations over a specified period.
-
B.
revenueLevel
chosen
Indicates the relative amount or tier of revenue associated with an entity or activity.
-
C.
majorRevenueSource
Indicates that one entity serves as the primary or dominant source of revenue for another entity.
-
D.
revenueSources
Indicates the relationship identifying where an entity’s revenue comes from or the different streams that generate its income.
-
E.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7221c081908068e66fe720f26d |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.