Triple
T1061071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Baseball owners |
E22907
|
entity |
| Predicate | collectivelyForm |
P10664
|
FINISHED |
| Object | Major League Baseball ownership |
—
|
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: Major League Baseball ownership | Statement: [Major League Baseball owners, collectivelyForm, Major League Baseball ownership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectivelyForm Context triple: [Major League Baseball owners, collectivelyForm, Major League Baseball ownership]
-
A.
usedCollectiveName
Indicates that a group of entities is referred to by a shared collective name.
-
B.
collectiveBody
chosen
Indicates that multiple individuals are grouped and act together as a single collective entity or body.
-
C.
formsSwarms
Indicates that multiple entities come together to create or participate in a coordinated swarm.
-
D.
formedByUnionOf
Indicates that something is created or defined as the union or combination of multiple other things.
-
E.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4ba6e35ac8190802341c31bda0e3b |
completed | March 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69a4b7340a048190807363f19d17a58f |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.