Triple
T27227000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellen MacArthur |
E682041
|
entity |
| Predicate | recordTime |
P99894
|
FINISHED |
| Object | 71 days 14 hours 18 minutes 33 seconds |
—
|
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: 71 days 14 hours 18 minutes 33 seconds | Statement: [Ellen MacArthur, recordTime, 71 days 14 hours 18 minutes 33 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordTime Context triple: [Ellen MacArthur, recordTime, 71 days 14 hours 18 minutes 33 seconds]
-
A.
recordDuration
chosen
Indicates the length of time for which something is recorded or captured.
-
B.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
-
C.
recordRun
Indicates that an entity logs or stores information about a particular execution or run of a process or activity.
-
D.
recordAttempt
Indicates an action where an attempt or trial is logged or stored as a record, typically capturing that the attempt occurred and possibly its outcome.
-
E.
recorded
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 9:44 a.m.