Triple
T5643123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Stars |
E124315
|
entity |
| Predicate | preIntegration |
P65379
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [St. Louis Stars, preIntegration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preIntegration Context triple: [St. Louis Stars, preIntegration, true]
-
A.
preludeTo
Indicates that one event, action, or state occurs earlier and serves as an introduction or lead-in to another.
-
B.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
C.
precondition
Indicates that one event, state, or condition must be true or occur before another event, state, or condition can validly or successfully take place.
-
D.
preDraftProcess
Indicates the procedural steps or activities that occur before a draft is created or formally written.
-
E.
pretext
Indicates that one party uses a stated reason or excuse to conceal their true motive for an action or decision.
- F. None of above. chosen
Provenance (4 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022a7cd9c819087f86f60e8b65fc3 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0727bc8190b16e9a669c04b4dd |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:41 p.m.