Triple
T7994816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puma corporate campus |
E186096
|
entity |
| Predicate | corporateFormOfOwner |
P30194
|
FINISHED |
| Object | public company |
—
|
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: public company | Statement: [Puma corporate campus, corporateFormOfOwner, public company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corporateFormOfOwner Context triple: [Puma corporate campus, corporateFormOfOwner, public company]
-
A.
ownershipStructure
Indicates how ownership or control is distributed among entities within an organization or asset.
-
B.
hasUnderlyingCompanyLegalForm
chosen
Indicates that an entity is associated with, or governed by, a specific underlying legal form of a company.
-
C.
organizationTypeOfOwner
Indicates the type or category of organization that owns a given entity.
-
D.
belongsToCompanyLegalForm
Indicates that an entity is associated with or classified under a specific legal form of a company.
-
E.
corporateStructure
Indicates how entities are organized, controlled, and related within a corporate hierarchy or ownership structure.
- 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_69ca829c6c308190ab05b43d234c52b2 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c73ba388190bcedc29fbdd22f3c |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:17 p.m.