Triple
T7512325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lark Force |
E177549
|
entity |
| Predicate | dateOverrun |
P28198
|
FINISHED |
| Object | 1942-01-23 |
—
|
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: 1942-01-23 | Statement: [Lark Force, dateOverrun, 1942-01-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOverrun Context triple: [Lark Force, dateOverrun, 1942-01-23]
-
A.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
B.
hasDeadline
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
C.
endedDueTo
Indicates that an event, process, or state came to a conclusion specifically because of a particular cause or condition.
-
D.
heldOver
chosen
Indicates that something has been continued, carried forward, or extended in effect or duration beyond its original or expected time.
-
E.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
- 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_69c69f276b108190af2cc790b6554544 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5d52b2c8190ba32b1575756fa7c |
completed | March 27, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:45 p.m.