Triple
T24569992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | convoy JW 55B |
E607907
|
entity |
| Predicate | escortType |
P156385
|
FINISHED |
| Object | close escort |
—
|
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: close escort | Statement: [convoy JW 55B, escortType, close escort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escortType Context triple: [convoy JW 55B, escortType, close escort]
-
A.
escortDuty
Indicates that one entity is responsible for accompanying and protecting another entity during travel or movement.
-
B.
hasChauffeur
Indicates that one entity employs or uses another entity to drive them or their vehicle as a chauffeur.
-
C.
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.
-
D.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
E.
transportIncludes
Indicates that a broader transport operation or service encompasses, contains, or makes use of a specific transport segment, mode, or component as part of its overall movement.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a923635c819097ecac0c82ec5f29 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:28 a.m.