Triple
T31850719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pershing Square Capital Management |
E813057
|
entity |
| Predicate | listedVehicle |
P172665
|
FINISHED |
| Object | Pershing Square Holdings, Ltd. |
—
|
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: Pershing Square Holdings, Ltd. | Statement: [Pershing Square Capital Management, listedVehicle, Pershing Square Holdings, Ltd.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listedVehicle Context triple: [Pershing Square Capital Management, listedVehicle, Pershing Square Holdings, Ltd.]
-
A.
usedVehicleModel
Indicates that a vehicle is a pre-owned (used) instance of a particular vehicle model.
-
B.
shortlistedVehicle
Indicates that a vehicle has been selected as a candidate option from a larger set, typically for further consideration or evaluation.
-
C.
vehicleUsed
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
-
D.
producedVehicle
Indicates that one entity manufactured or created a particular vehicle.
-
E.
vehicleBase
Indicates that one entity serves as the foundational or underlying base for a vehicle-related entity or system.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b03c50ac8190a21a7721219b0167 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:51 p.m.