Triple
T31933795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Trevisani |
E815328
|
entity |
| Predicate | hasMajorityStakeIn |
P17177
|
FINISHED |
| Object | New Mexico United |
—
|
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 Mexico United | Statement: [Peter Trevisani, hasMajorityStakeIn, New Mexico United]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorityStakeIn Context triple: [Peter Trevisani, hasMajorityStakeIn, New Mexico United]
-
A.
majorityHolding
Indicates that one entity owns more than half of another entity’s voting shares or equity, giving it effective control over that entity.
-
B.
hasMajorityIn
chosen
Indicates that one entity holds more than half of the control, ownership, or representation within another entity or group.
-
C.
majorShareholderOf
Indicates that one entity owns a controlling or significantly large portion of another entity’s shares or equity.
-
D.
isOwnedMajorityBy
Indicates that one entity holds more than half of the ownership or controlling interest in another entity.
-
E.
hasMajorityOf
Indicates that one entity possesses or controls more than half of the total quantity, members, or share of another entity.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a005b2e0a9c819081c6f7ccbef49ff8 |
completed | May 10, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a005a8bcde88190ace2bc0215e26430 |
completed | May 10, 2026, 10:14 a.m. |
Created at: May 1, 2026, 12:04 a.m.