Triple
T14153202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy helicopter squadrons |
E350740
|
entity |
| Predicate | operateFrom |
P6602
|
FINISHED |
| Object | aircraft carriers |
—
|
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: aircraft carriers | Statement: [Royal Navy helicopter squadrons, operateFrom, aircraft carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operateFrom Context triple: [Royal Navy helicopter squadrons, operateFrom, aircraft carriers]
-
A.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
B.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
C.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
D.
operatedFrom
chosen
Indicates that an entity conducted its activities or operations starting from or based at a particular location or source.
-
E.
formerOperates
Indicates that an entity previously operated or managed another entity but no longer does so.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6133754881908e1e97db71772deb |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:57 a.m.