Triple
T7444576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freedom Rock |
E171840
|
entity |
| Predicate | hasRepaintingFrequency |
P29070
|
FINISHED |
| Object | annually |
—
|
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: annually | Statement: [Freedom Rock, hasRepaintingFrequency, annually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepaintingFrequency Context triple: [Freedom Rock, hasRepaintingFrequency, annually]
-
A.
hasEventFrequency
chosen
Indicates how often a particular event occurs within a given time period.
-
B.
replayFrequency
Indicates how often an event, action, or sequence is repeated or played back over a given period.
-
C.
supportsVariableRefreshRate
Indicates that one entity provides compatibility with or functionality for dynamically adjusting refresh rates in coordination with another entity.
-
D.
hasFrequencyCategory
Indicates that something is associated with a particular classification of how often it occurs or is used.
-
E.
displayRefreshRate
Indicates the frequency at which a display updates its visual content, typically measured in hertz (Hz).
- 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_69c68a65402881908f7869368eb746fb |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f36e9a588190b54b8bae181fc971 |
completed | March 27, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:14 p.m.