Triple
T25054873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia League |
E627488
|
entity |
| Predicate | precededByInProminence |
P11124
|
FINISHED |
| Object | Federal League |
—
|
NE NERFINISHED |
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: Federal League | Statement: [Columbia League, precededByInProminence, Federal League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByInProminence Context triple: [Columbia League, precededByInProminence, Federal League]
-
A.
precededBySpecial
Indicates that one event or entity occurs immediately before another in a context marked as special or exceptional compared to normal ordering.
-
B.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
C.
precededByDocument
Indicates that one document occurs or is issued earlier in sequence or time than another document.
-
D.
precededByUse
Indicates that one use, action, or event occurs earlier in time and is directly followed by another specified use, action, or event.
-
E.
appearsBefore
chosen
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 6:09 a.m.