Triple
T1305618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RYA |
E27868
|
entity |
| Predicate | hasUnderlyingOwnershipType |
P7585
|
FINISHED |
| Object | public 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: public company | Statement: [RYA, hasUnderlyingOwnershipType, public company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderlyingOwnershipType Context triple: [RYA, hasUnderlyingOwnershipType, public company]
-
A.
ownershipType
chosen
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
B.
hasCapitalType
Indicates that a specified location’s capital is of a particular type (e.g., political, administrative, or economic capital).
-
C.
hasComplexOwnershipStructure
Indicates that an entity’s ownership is arranged through multiple layers, parties, or instruments such that control or equity interests are not straightforward to determine.
-
D.
hasUnderlyingLEI
Indicates that an entity is associated with, or identified by, a specific underlying Legal Entity Identifier (LEI).
-
E.
isStateOwned
Indicates that an entity is owned or controlled by a government or state authority.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c13524d481909e8f5bb2ab91f6e4 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.