Triple
T35058412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miramar Group |
E1011526
|
entity |
| Predicate | typeOfConglomerate |
P203457
|
FINISHED |
| Object | privately held 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: privately held company | Statement: [Miramar Group, typeOfConglomerate, privately held company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfConglomerate Context triple: [Miramar Group, typeOfConglomerate, privately held company]
-
A.
typeOfCluster
Indicates that one entity is classified as a specific kind or category of cluster in relation to another entity.
-
B.
conceptualType
Indicates that one entity represents the conceptual category, class, or abstract type to which another entity belongs.
-
C.
groupingType
Indicates how multiple entities are categorized or clustered together based on a shared grouping criterion.
-
D.
unificationType
Indicates the specific manner or category in which two or more entities are combined, merged, or treated as a single unified whole.
-
E.
typeOfEnsemble
Indicates the specific kind or category of ensemble that an entity belongs to or represents.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01839b071481909f9cc79a6a09387d |
completed | May 11, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_6a017edbed688190baa61cbae5110c8e |
completed | May 11, 2026, 7:01 a.m. |
| PDg | Predicate description generation | batch_6a01839a63a48190a59a6c4464db0eea |
completed | May 11, 2026, 7:22 a.m. |
Created at: May 3, 2026, 4:01 p.m.