Triple
T32053958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy frigates |
E818564
|
entity |
| Predicate | canEscort |
P33337
|
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 frigates, canEscort, aircraft carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canEscort Context triple: [Royal Navy frigates, canEscort, aircraft carriers]
-
A.
hiresAsEscort
Indicates that one entity employs another specifically to provide escort or companionship services.
-
B.
escortDuty
chosen
Indicates that one entity is responsible for accompanying and protecting another entity during travel or movement.
-
C.
numberOfEscorts
Indicates the quantity of escorting entities or units associated with a given entity or event.
-
D.
escortType
Indicates the specific role or category of escort service associated with an escorting relationship or activity.
-
E.
escortDuties
Indicates that one entity is responsible for accompanying and ensuring the safe or guided movement of another entity from one place or situation to another.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4ed587c8190868dba58046328c9 |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:21 a.m.