Triple
T32097179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Ring |
E819748
|
entity |
| Predicate | timeframeOfUse |
P173558
|
FINISHED |
| Object | Second Age |
—
|
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: Second Age | Statement: [Red Ring, timeframeOfUse, Second Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeframeOfUse Context triple: [Red Ring, timeframeOfUse, Second Age]
-
A.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
B.
timeframeApproximate
Indicates that the time period associated with an event or relation is not exact but only roughly or loosely specified.
-
C.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
D.
recommendedUsageTime
Indicates the period of time for which something is advised or intended to be used.
-
E.
typicalUseDays
Indicates the usual or expected number of days over which something is used or intended to be used.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b643d5008190b789f0a4d3288fa3 |
completed | May 3, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:26 a.m.