Triple
T31004693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tall Ship Glenlee |
E790035
|
entity |
| Predicate | flagAtLaunch |
P170900
|
FINISHED |
| Object | United Kingdom |
—
|
NE NERFINISHED |
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: United Kingdom | Statement: [The Tall Ship Glenlee, flagAtLaunch, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagAtLaunch Context triple: [The Tall Ship Glenlee, flagAtLaunch, United Kingdom]
-
A.
flagshipAt
Indicates that a particular entity serves as the primary or leading representative (flagship) of something at or for a specified location, organization, or context.
-
B.
flagUsedBy
Indicates that a particular flag is officially used by a specified entity, such as a country, organization, or group.
-
C.
flagStatus
Indicates the current state or condition assigned to a flag, such as whether it is active, raised, set, or marked in a particular way.
-
D.
flagUsedIn
Indicates that a particular flag is employed or referenced within a given context, such as a program, configuration, or process.
-
E.
flag
Indicates that one entity marks, signals, or draws attention to another entity, often to denote status, importance, or the need for review or action.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:57 p.m.