Triple
T5069799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jump Salty |
E114244
|
entity |
| Predicate | hasLengthApproximate |
P4874
|
FINISHED |
| Object | about 30 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 30 minutes | Statement: [Jump Salty, hasLengthApproximate, about 30 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLengthApproximate Context triple: [Jump Salty, hasLengthApproximate, about 30 minutes]
-
A.
hasMaxLengthApprox
Indicates that something has a maximum length that is approximately equal to a specified value, allowing for some tolerance or imprecision.
-
B.
hasApproximateValue
Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
-
C.
hasApproximateNumberOfLetters
Indicates that an entity is associated with a number that roughly, but not exactly, corresponds to the count of letters it contains.
-
D.
hasDimensionsApprox
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
-
E.
hasApproximateDuration
chosen
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd749f47908190891ac8432c5b5615 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.