Triple
T11515413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Beamon |
E273017
|
entity |
| Predicate | recordDuration |
P99894
|
FINISHED |
| Object | nearly 23 years |
—
|
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: nearly 23 years | Statement: [Bob Beamon, recordDuration, nearly 23 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordDuration Context triple: [Bob Beamon, recordDuration, nearly 23 years]
-
A.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
B.
maximumRecordedLength
Indicates the greatest length value that has been observed and recorded for the entity in question.
-
C.
lengthInSeconds
Indicates that one entity specifies the duration of another entity measured in seconds.
-
D.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
-
E.
mainRecordingPeriod
Indicates the primary time span during which the recording activity took place.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db8bf9c8190820c289e6b0c3873 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.