Triple
T5842448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PUM |
E129624
|
entity |
| Predicate | underlyingCompanyType |
P66662
|
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: [PUM, underlyingCompanyType, public company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingCompanyType Context triple: [PUM, underlyingCompanyType, public company]
-
A.
underlyingCompany
Indicates that one entity serves as the fundamental or base company upon which another entity (such as a product, instrument, or structure) is built, derived, or dependent.
-
B.
underlyingCompanyName
Indicates the name of the company that serves as the foundational or primary entity underlying another entity, structure, or instrument.
-
C.
backedCompanyType
Indicates the type or category of company that is being financially supported or invested in by another party.
-
D.
industryOfUnderlyingCompany
Indicates the industry sector in which the underlying company associated with this entity operates.
-
E.
underlyingCompanyService
Indicates that one entity functions as a foundational or supporting service for another company or business entity.
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c03c8d579081909d7b97fc9014b5d7 |
completed | March 22, 2026, 7:01 p.m. |
Created at: March 22, 2026, 3:54 p.m.