Triple
T33602941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crew (Memphis Raines’ team) |
E860769
|
entity |
| Predicate | missionDeadline |
P8546
|
FINISHED |
| Object | 72 hours |
—
|
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: 72 hours | Statement: [The Crew (Memphis Raines’ team), missionDeadline, 72 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionDeadline Context triple: [The Crew (Memphis Raines’ team), missionDeadline, 72 hours]
-
A.
hasDeadline
chosen
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
B.
notificationDeadline
Indicates the time or date by which a required notification must be sent or received.
-
C.
dateOfUltimatum
Indicates the specific date on which an ultimatum was issued, delivered, or came into effect in the relationship between the involved parties.
-
D.
postDeadlineRule
Indicates a rule or policy that applies to actions or conditions occurring after a specified deadline has passed.
-
E.
missionDuration
Indicates the length of time over which a mission or operation takes place from start to finish.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:41 a.m.