Triple
T31798140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Yanks |
E811655
|
entity |
| Predicate | assetsMergedInto |
P12293
|
FINISHED |
| Object | New York Bulldogs |
—
|
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: New York Bulldogs | Statement: [Boston Yanks, assetsMergedInto, New York Bulldogs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assetsMergedInto Context triple: [Boston Yanks, assetsMergedInto, New York Bulldogs]
-
A.
sharesMergedWith
Indicates that one entity’s shares have been combined or consolidated with another entity’s shares, typically as part of a merger or similar corporate action.
-
B.
consolidatedAs
chosen
Indicates that one entity has been combined, merged, or unified into another entity to form a single consolidated whole.
-
C.
demergedInto
Indicates that an entity has been split or separated into one or more distinct successor entities as a result of a demerger process.
-
D.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
E.
laterMergedWith
Indicates that one entity was combined into and became part of another entity at a subsequent point in 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:41 p.m.