Triple
T37676185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilson A2000 |
E938099
|
entity |
| Predicate | typicalBreakInTime |
P204337
|
FINISHED |
| Object | moderate to long |
—
|
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: moderate to long | Statement: [Wilson A2000, typicalBreakInTime, moderate to long]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBreakInTime Context triple: [Wilson A2000, typicalBreakInTime, moderate to long]
-
A.
typicalBreaks
Indicates that an entity commonly or characteristically causes a break, interruption, or failure in another entity or process.
-
B.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
C.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
D.
breakType
Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
-
E.
typicalDurationMinutes
Indicates the usual or expected length of time, measured in minutes, that an event, activity, or process typically lasts.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.