Triple
T8290272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long-Term Servicing Branch |
E193875
|
entity |
| Predicate | featureUpdateCadence |
P56156
|
FINISHED |
| Object | very infrequent |
—
|
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: very infrequent | Statement: [Long-Term Servicing Branch, featureUpdateCadence, very infrequent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureUpdateCadence Context triple: [Long-Term Servicing Branch, featureUpdateCadence, very infrequent]
-
A.
typicalUpdateFrequency
chosen
Indicates how often an entity is usually updated or refreshed over time.
-
B.
updatedEvery
Indicates that something is refreshed or brought up to date at a regular, specified interval.
-
C.
rankingUpdateFrequency
Indicates how often the ranking or ordered list associated with an entity is recalculated or refreshed.
-
D.
standardReleaseCadence
Indicates a relationship where an entity follows a regular, predefined schedule or frequency for releasing updates or versions.
-
E.
serviceFrequencyType
Indicates how often a service occurs or is scheduled within a given time 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c99fdd48190a3f304237be609a0 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:52 p.m.