Triple
T2630224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatr Mobile |
E59613
|
entity |
| Predicate | dataRollover |
P42349
|
FINISHED |
| Object | no on most base plans |
—
|
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: no on most base plans | Statement: [Chatr Mobile, dataRollover, no on most base plans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataRollover Context triple: [Chatr Mobile, dataRollover, no on most base plans]
-
A.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
B.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
C.
rotationPeriod_hours
Indicates the length of time, measured in hours, that an object takes to complete one full rotation on its axis.
-
D.
dataMaintained
Indicates that one entity is responsible for preserving, storing, or keeping another entity’s data up to date and accessible over time.
-
E.
leafRetention
Indicates whether an entity retains its leaves (e.g., remains evergreen) or sheds them seasonally.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdb0e7b888190bfa5d2e33f00ec0f |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd810d7f481908e81c305772c4c14 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abdb0bf9b881908b239c1310c7bbf3 |
completed | March 7, 2026, 8 a.m. |
Created at: March 6, 2026, 9:50 p.m.