Triple
T4649612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DANSKE |
E102259
|
entity |
| Predicate | companyLegalForm |
P51147
|
FINISHED |
| Object | Aktieselskab (A/S) |
—
|
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: Aktieselskab (A/S) | Statement: [DANSKE, companyLegalForm, Aktieselskab (A/S)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyLegalForm Context triple: [DANSKE, companyLegalForm, Aktieselskab (A/S)]
-
A.
legalForm
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
-
B.
belongsToCompanyLegalForm
chosen
Indicates that an entity is associated with or classified under a specific legal form of a company.
-
C.
previousLegalForm
Indicates the legal form or organizational status an entity had before its current legal form.
-
D.
legalPersonality
Indicates that an entity possesses recognized legal status, enabling it to hold rights, bear obligations, and act as a subject under the law.
-
E.
legalEstablishment
Indicates that an entity has been formally created, recognized, or brought into existence according to legal rules or procedures.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.