Triple
T2841269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Pedestal |
E62472
|
entity |
| Predicate | numberOfEscorts |
P42967
|
FINISHED |
| Object | more than 50 |
—
|
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: more than 50 | Statement: [Operation Pedestal, numberOfEscorts, more than 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfEscorts Context triple: [Operation Pedestal, numberOfEscorts, more than 50]
-
A.
escortDuty
Indicates that one entity is responsible for accompanying and protecting another entity during travel or movement.
-
B.
passengersCountApproximate
Indicates that the number of passengers involved is given as an approximate or estimated count rather than an exact figure.
-
C.
numberOfVenues
Indicates the total count of venues associated with a given entity or context.
-
D.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
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. 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf16d0c08190bb8de4a4160b4414 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde4895dc819097c396c5d31ac1d1 |
completed | March 7, 2026, 8:14 a.m. |
Created at: March 6, 2026, 10:01 p.m.