Triple
T16103257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Republic of Germany |
E390674
|
entity |
| Predicate | hasLegalFormForRailwayHolding |
P67327
|
FINISHED |
| Object | Aktiengesellschaft |
—
|
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: Aktiengesellschaft | Statement: [Federal Republic of Germany, hasLegalFormForRailwayHolding, Aktiengesellschaft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalFormForRailwayHolding Context triple: [Federal Republic of Germany, hasLegalFormForRailwayHolding, Aktiengesellschaft]
-
A.
hasLegalStructure
Indicates that an entity possesses a specific formal legal organization or classification under law.
-
B.
hasUnderlyingCompanyLegalForm
Indicates that an entity is associated with, or governed by, a specific underlying legal form of a company.
-
C.
belongsToCompanyLegalForm
Indicates that an entity is associated with or classified under a specific legal form of a company.
-
D.
hasParentCompanyLegalForm
Indicates that an entity’s parent company possesses a specific legal form or legal organizational type.
-
E.
typicalLegalForm
chosen
Indicates the standard or commonly used legal organizational form associated with an entity.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6a4b8881908e8dc186381196d8 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.