Triple
T198904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas Entertainment |
E4057
|
entity |
| Predicate | companyType |
P3580
|
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: [Atlas Entertainment, companyType, privately held company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyType Context triple: [Atlas Entertainment, companyType, privately held company]
-
A.
employerType
Indicates the classification or category of an employer in relation to the entity (e.g., public, private, nonprofit, self-employed).
-
B.
organizationType
chosen
Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
-
C.
company
Indicates that an entity is a business organization engaged in commercial, industrial, or professional activities.
-
D.
hasTypeOfOrganization
Indicates that an entity is classified as belonging to a particular type or category of organization.
-
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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25bcb2c7c8190b0e031e93651182a |
completed | Feb. 28, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69a25b4886b48190b46fd2244648a098 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.