Triple
T21249752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FWV 48 |
E523710
|
entity |
| Predicate | workApproximateDuration |
P32671
|
FINISHED |
| Object | about 40 minutes |
—
|
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: about 40 minutes | Statement: [FWV 48, workApproximateDuration, about 40 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workApproximateDuration Context triple: [FWV 48, workApproximateDuration, about 40 minutes]
-
A.
workLength
chosen
Indicates the duration or length of time associated with a particular work or task.
-
B.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
C.
projectLength
Indicates the duration or total time span over which a project is planned or executed.
-
D.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
E.
estimatedWorkingsLength
Indicates the expected or calculated duration or extent of the workings involved in a task, project, or operation.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359c7a648190b4345336ac3be024 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:56 p.m.