Triple
T28406828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CEO of Huawei |
E719550
|
entity |
| Predicate | employerLegalForm |
P64
|
FINISHED |
| Object | private 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: private company | Statement: [CEO of Huawei, employerLegalForm, private company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerLegalForm Context triple: [CEO of Huawei, employerLegalForm, private company]
-
A.
legalForm
chosen
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
-
B.
legalFormOfWork
Indicates the legally defined type or classification of employment or work arrangement under which an activity is performed.
-
C.
typicalLegalForm
Indicates the standard or commonly used legal organizational form associated with an entity.
-
D.
legalElement
Indicates that something is a constituent part or component required or recognized within a legal framework, rule, or process.
-
E.
businessForm
Indicates the legal or organizational structure under which a business operates (e.g., sole proprietorship, partnership, corporation).
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 1:24 a.m.