Triple
T7381032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omaha Cardinals |
E170249
|
entity |
| Predicate | affiliationEnd |
P71729
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [Omaha Cardinals, affiliationEnd, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affiliationEnd Context triple: [Omaha Cardinals, affiliationEnd, 1959]
-
A.
affiliationEndedWith
chosen
Indicates that a previously existing affiliation or association between entities has come to an end at a specific point in time or under certain conditions.
-
B.
affiliationStart
Indicates the point in time when an entity’s formal association or membership with another entity begins.
-
C.
administrativeAffiliation
Indicates that one entity is formally connected to, governed by, or overseen by another entity within an administrative or organizational structure.
-
D.
laterAffiliation
Indicates that an entity becomes affiliated with another entity at a later time than a previously mentioned or initial affiliation.
-
E.
affiliationNote
Indicates a textual note or qualifier that provides additional context or clarification about an affiliation relationship between entities.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1c7b5bc81908afa2bf39159979b |
completed | March 27, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:08 p.m.