Triple
T22664254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal Expos |
E559740
|
entity |
| Predicate | expansionClass |
P149129
|
FINISHED |
| Object | 1969 MLB expansion |
—
|
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: 1969 MLB expansion | Statement: [Montreal Expos, expansionClass, 1969 MLB expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionClass Context triple: [Montreal Expos, expansionClass, 1969 MLB expansion]
-
A.
expandsClass
Indicates that one class broadens or extends the definition, scope, or functionality of another class.
-
B.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
C.
expansionUnit
Indicates a unit or component that serves to extend, enlarge, or add capacity to another system, structure, or entity.
-
D.
expansionSystem
Indicates a relationship where a system undergoes or enables expansion, typically by increasing its scope, capacity, or components over time.
-
E.
expansionStrategy
Indicates the approach or method an entity uses to grow or extend its presence, operations, or influence.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f176617ed8819095a58a2c9f1e3918 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:08 p.m.