Triple
T26374269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 303 Squadron maintenance personnel |
E660850
|
entity |
| Predicate | workedShifts |
P7950
|
FINISHED |
| Object | around-the-clock as required by operations |
—
|
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: around-the-clock as required by operations | Statement: [No. 303 Squadron maintenance personnel, workedShifts, around-the-clock as required by operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workedShifts Context triple: [No. 303 Squadron maintenance personnel, workedShifts, around-the-clock as required by operations]
-
A.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
B.
workPeriod
chosen
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
C.
workedFrom
Indicates that an entity was employed or actively engaged in work starting from a specified point in time.
-
D.
timePeriodOfWorks
Indicates the span of time during which the associated works were created, produced, or active.
-
E.
workAfter
Indicates that one entity performs its work or begins an activity only after another specified entity has completed or started its own work.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 11 p.m.