Triple
T6585779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Herb |
E159214
|
entity |
| Predicate | typicalTrackLengthRange |
P71633
|
FINISHED |
| Object | 3–5 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: 3–5 minutes | Statement: [International Herb, typicalTrackLengthRange, 3–5 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTrackLengthRange Context triple: [International Herb, typicalTrackLengthRange, 3–5 minutes]
-
A.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
B.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
trackLengthApproxKm
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
-
D.
trailLengthApprox
Indicates an approximate measurement of the total length of a trail.
-
E.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
- 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6c07bb434819096ec3e3b966042a5 |
completed | March 27, 2026, 5:38 p.m. |
Created at: March 27, 2026, 1:54 p.m.