Triple
T1305631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RYAAY |
E27869
|
entity |
| Predicate | isADRFor |
P26830
|
FINISHED |
| Object | Ryanair Holdings plc ordinary shares |
—
|
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: Ryanair Holdings plc ordinary shares | Statement: [RYAAY, isADRFor, Ryanair Holdings plc ordinary shares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isADRFor Context triple: [RYAAY, isADRFor, Ryanair Holdings plc ordinary shares]
-
A.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
B.
hasInternationalDistrict
Indicates that an entity possesses, contains, or is associated with a designated international district within its boundaries or scope.
-
C.
appliesToSovereignState
Indicates that something (such as a rule, status, or attribute) is applicable to, or in effect for, a sovereign state.
-
D.
appliesToPersonNationality
Indicates that something is relevant or applicable specifically to a person’s nationality.
-
E.
displayedInCountry
Indicates that something is shown, exhibited, or made visible within the boundaries of a specified country.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:51 p.m.