Triple
T19203547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dayton Aeros |
E480170
|
entity |
| Predicate | foundedAsNameFor |
P364
|
FINISHED |
| Object | WHA expansion franchise |
—
|
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: WHA expansion franchise | Statement: [Dayton Aeros, foundedAsNameFor, WHA expansion franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsNameFor Context triple: [Dayton Aeros, foundedAsNameFor, WHA expansion franchise]
-
A.
foundedAs
chosen
Indicates the original name or form under which an organization, institution, or entity was first established.
-
B.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
C.
foundedAsCurrentName
Indicates that an entity was originally founded under the same name it currently has, without having undergone a name change.
-
D.
foundedFrom
Indicates that an entity was established or originated starting from a particular source, place, or prior entity.
-
E.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f99a571c8190a1d53eb1994e0058 |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:15 p.m.