Triple
T5016020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | App Store Review Guidelines |
E112741
|
entity |
| Predicate | changeFrequency |
P56156
|
FINISHED |
| Object | updated periodically |
—
|
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: updated periodically | Statement: [App Store Review Guidelines, changeFrequency, updated periodically]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeFrequency Context triple: [App Store Review Guidelines, changeFrequency, updated periodically]
-
A.
rankingUpdateFrequency
Indicates how often the ranking or ordered list associated with an entity is recalculated or refreshed.
-
B.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
C.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
D.
typicalUpdateFrequency
chosen
Indicates how often an entity is usually updated or refreshed over time.
-
E.
replacedFrequency
Indicates how often one entity is substituted for or takes the place of another over a given period.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732f4c5c8190b90f8e4daab458ee |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.