Triple
T38543296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schaumburg Flyers |
E924894
|
entity |
| Predicate | homeFieldNameDuringTenure |
P22315
|
FINISHED |
| Object | Alexian Field |
—
|
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: Alexian Field | Statement: [Schaumburg Flyers, homeFieldNameDuringTenure, Alexian Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFieldNameDuringTenure Context triple: [Schaumburg Flyers, homeFieldNameDuringTenure, Alexian Field]
-
A.
homeFieldName
chosen
Indicates the name of the field or venue that serves as an entity’s home location for its activities or events.
-
B.
residenceDuringCareer
Indicates the place where an individual lived for a significant period while pursuing their professional career.
-
C.
lifeTenure
Indicates that an individual holds a position or office for the duration of their lifetime, without a fixed term limit or routine reappointment.
-
D.
tenureCharacteristic
Indicates a relationship where a specific attribute or quality characterizes the duration or conditions of someone’s or something’s tenure.
-
E.
denotesTenure
Indicates that one entity holds or has held a position, role, or office at another entity for a specified period of time.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.